From: Kui-Feng Lee <kuifeng@fb.com>
To: "daniel@iogearbox.net" <daniel@iogearbox.net>,
Yonghong Song <yhs@fb.com>, Kernel Team <Kernel-team@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"andrii@kernel.org" <andrii@kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v8 5/5] bpftool: Show parameters of BPF task iterators.
Date: Wed, 31 Aug 2022 01:11:16 +0000 [thread overview]
Message-ID: <abba7eb0540bda61c653fa42abd3bdd552438208.camel@fb.com> (raw)
In-Reply-To: <56e56327-cfed-3e78-84ca-db45ac5662c9@fb.com>
On Tue, 2022-08-30 at 16:56 -0700, Yonghong Song wrote:
>
>
> On 8/29/22 12:23 PM, Kui-Feng Lee wrote:
> > Show tid or pid of iterators if giving an argument of tid or pid
> >
> > For example, the command `bpftool link list` may list following
> > lines.
> >
> > 1: iter prog 2 target_name bpf_map
> > 2: iter prog 3 target_name bpf_prog
> > 33: iter prog 225 target_name task_file tid 1644
> > pids test_progs(1644)
> >
> > Link 33 is a task_file iterator with tid 1644. For now, only
> > targets
> > of task, task_file and task_vma may be with tid or pid to filter
> > out
> > tasks other than those belonging to a process (pid) or a thread
> > (tid).
> >
> > Signed-off-by: Kui-Feng Lee <kuifeng@fb.com>
>
> Please rebase on top of bpf-next as the bpf_iter cgroup support
> is just merged which will cause a conflict with this patch.
>
> Acked-by: Yonghong Song <yhs@fb.com>
Tnank you! Just rebased the code.
prev parent reply other threads:[~2022-08-31 1:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 19:23 [PATCH bpf-next v8 0/5] Parameterize task iterators Kui-Feng Lee
2022-08-29 19:23 ` [PATCH bpf-next v8 1/5] bpf: " Kui-Feng Lee
2022-08-30 23:54 ` Yonghong Song
2022-08-31 0:35 ` Kui-Feng Lee
2022-08-31 2:37 ` Yonghong Song
2022-08-31 3:59 ` Yonghong Song
2022-08-31 16:39 ` Kui-Feng Lee
2022-08-29 19:23 ` [PATCH bpf-next v8 2/5] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-08-29 19:23 ` [PATCH bpf-next v8 3/5] bpf: Handle show_fdinfo " Kui-Feng Lee
2022-08-30 0:56 ` Kui-Feng Lee
2022-08-30 0:58 ` Kui-Feng Lee
2022-08-30 21:17 ` Yonghong Song
2022-08-29 19:23 ` [PATCH bpf-next v8 4/5] selftests/bpf: Test " Kui-Feng Lee
2022-08-30 22:54 ` Yonghong Song
2022-08-29 19:23 ` [PATCH bpf-next v8 5/5] bpftool: Show parameters of BPF task iterators Kui-Feng Lee
2022-08-30 16:52 ` Quentin Monnet
2022-08-31 1:10 ` Kui-Feng Lee
2022-08-30 23:56 ` Yonghong Song
2022-08-31 1:11 ` Kui-Feng Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abba7eb0540bda61c653fa42abd3bdd552438208.camel@fb.com \
--to=kuifeng@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox