From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kui-Feng Lee <kuifeng@fb.com>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kernel-team@fb.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v11 0/5] Parameterize task iterators.
Date: Tue, 27 Sep 2022 12:33:39 -0700 [thread overview]
Message-ID: <7fb1f18c-a695-494d-0242-b782d410250c@linux.dev> (raw)
In-Reply-To: <20220926184957.208194-1-kuifeng@fb.com>
On 9/26/22 11:49 AM, 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 additional
> parameters, people can now create an iterator to go through all
> resources or only the resources of a task.
Acked-by: Martin KaFai Lau <martin.lau@kernel.org>
next prev parent reply other threads:[~2022-09-27 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:49 [PATCH bpf-next v11 0/5] Parameterize task iterators Kui-Feng Lee
2022-09-26 18:49 ` [PATCH bpf-next v11 1/5] bpf: " Kui-Feng Lee
2022-09-28 23:36 ` Andrii Nakryiko
2022-09-26 18:49 ` [PATCH bpf-next v11 2/5] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-09-26 18:49 ` [PATCH bpf-next v11 3/5] bpf: Handle show_fdinfo " Kui-Feng Lee
2022-09-26 18:49 ` [PATCH bpf-next v11 4/5] selftests/bpf: Test " Kui-Feng Lee
2022-09-26 18:49 ` [PATCH bpf-next v11 5/5] bpftool: Show parameters of BPF task iterators Kui-Feng Lee
2022-09-27 19:33 ` Martin KaFai Lau [this message]
2022-09-28 23:40 ` [PATCH bpf-next v11 0/5] Parameterize " patchwork-bot+netdevbpf
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=7fb1f18c-a695-494d-0242-b782d410250c@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=kuifeng@fb.com \
--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