From: Kui-Feng Lee <kuifeng@fb.com>
To: "daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>, Yonghong Song <yhs@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 v2 0/3] Parameterize task iterators.
Date: Mon, 1 Aug 2022 23:35:02 +0000 [thread overview]
Message-ID: <f92e20e9961963e20766e290ee6668edd4bacf06.camel@fb.com> (raw)
In-Reply-To: <20220801232649.2306614-1-kuifeng@fb.com>
On Mon, 2022-08-01 at 16:26 -0700, Kui-Feng Lee wrote:
> Allow creating an iterator that loops through resources of one
> task/thread.
>
> People could only create iterators to loop through all resources of
> files, vma, and tasks in the system, even though they were interested
> in only the
> resources of a specific task or process. Passing the addintional
> parameters, people can now create an iterator to go through all
> resources or only the resources of a task.
>
> Major Changes:
>
> - Add new parameters in bpf_iter_link_info to indicate to go through
> all tasks or to go through a specific task.
>
> - Change the implementations of BPF iterators of vma, files, and
> tasks to allow going through only the resources of a specific
> task.
>
> - Provide the arguments of parameterized task iterators in
> bpf_link_info.
The major changes since v1:
- Fix the issue of task_seq_get_next() returning NULL for being called
twice or more.
- Use pidfd instead of pid/tid while keep the 'type'.
>
> Kui-Feng Lee (3):
> bpf: Parameterize task iterators.
> bpf: Handle bpf_link_info for the parameterized task BPF iterators.
> selftests/bpf: Test parameterized task BPF iterators.
>
> include/linux/bpf.h | 4 +
> include/uapi/linux/bpf.h | 27 ++++
> kernel/bpf/task_iter.c | 103 ++++++++++---
> tools/include/uapi/linux/bpf.h | 27 ++++
> .../selftests/bpf/prog_tests/bpf_iter.c | 143 +++++++++++++++-
> --
> .../selftests/bpf/prog_tests/btf_dump.c | 2 +-
> .../selftests/bpf/progs/bpf_iter_task.c | 9 ++
> .../selftests/bpf/progs/bpf_iter_task_file.c | 7 +
> .../selftests/bpf/progs/bpf_iter_task_vma.c | 6 +-
> 9 files changed, 282 insertions(+), 46 deletions(-)
>
prev parent reply other threads:[~2022-08-01 23:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 23:26 [PATCH bpf-next v2 0/3] Parameterize task iterators Kui-Feng Lee
2022-08-01 23:26 ` [PATCH bpf-next v2 1/3] bpf: " Kui-Feng Lee
2022-08-02 1:49 ` Alexei Starovoitov
2022-08-02 16:47 ` Kui-Feng Lee
2022-08-02 21:19 ` Andrii Nakryiko
2022-08-02 3:30 ` Andrii Nakryiko
2022-08-02 16:42 ` Kui-Feng Lee
2022-08-02 21:17 ` Andrii Nakryiko
2022-08-04 23:05 ` Kui-Feng Lee
2022-08-01 23:26 ` [PATCH bpf-next v2 2/3] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-08-01 23:26 ` [PATCH bpf-next v2 3/3] selftests/bpf: Test " Kui-Feng Lee
2022-08-01 23:35 ` 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=f92e20e9961963e20766e290ee6668edd4bacf06.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;
as well as URLs for NNTP newsgroup(s).