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 v7 4/5] selftests/bpf: Test parameterized task BPF iterators.
Date: Sat, 27 Aug 2022 18:33:43 +0000 [thread overview]
Message-ID: <b453f23f1d78b40616e8d55649eed117a4925133.camel@fb.com> (raw)
In-Reply-To: <6a783eea-dd72-eb8c-7ce4-8dfb06bb1fa7@fb.com>
On Fri, 2022-08-26 at 14:24 -0700, Yonghong Song wrote:
>
>
> On 8/25/22 5:37 PM, Kui-Feng Lee wrote:
> > Test iterators of vma, files, and tasks of tasks.
>
> 'tasks of tasks' is confusing.
> I guess you mean:
> Test iterators of (1). vma, files and tasks of a process,
> (2). vma, files of a task, and (3). a single task.
> ?
"Test iterators of vma, files and tasks."
It would be enough since the following lines explains the effects of
the parameters.
>
> >
> > Ensure the API works appropriately to visit all tasks,
> > tasks in a process, or a particular task.
> >
> > Signed-off-by: Kui-Feng Lee <kuifeng@fb.com>
> > ---
> > .../selftests/bpf/prog_tests/bpf_iter.c | 282
> > ++++++++++++++++--
> > .../selftests/bpf/prog_tests/btf_dump.c | 2 +-
> > .../selftests/bpf/progs/bpf_iter_task.c | 9 +
> > .../selftests/bpf/progs/bpf_iter_task_file.c | 9 +-
> > .../selftests/bpf/progs/bpf_iter_task_vma.c | 7 +-
> > .../selftests/bpf/progs/bpf_iter_vma_offset.c | 37 +++
> > 6 files changed, 322 insertions(+), 24 deletions(-)
> > create mode 100644
> > tools/testing/selftests/bpf/progs/bpf_iter_vma_offset.c
> >
> [...]
next prev parent reply other threads:[~2022-08-27 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 0:37 [PATCH bpf-next v7 0/5] Parameterize task iterators Kui-Feng Lee
2022-08-26 0:37 ` [PATCH bpf-next v7 1/5] bpf: " Kui-Feng Lee
2022-08-26 19:30 ` Yonghong Song
2022-08-27 18:29 ` Kui-Feng Lee
2022-08-26 0:37 ` [PATCH bpf-next v7 2/5] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-08-26 0:37 ` [PATCH bpf-next v7 3/5] bpf: Handle show_fdinfo " Kui-Feng Lee
2022-08-26 19:49 ` Yonghong Song
2022-08-26 0:37 ` [PATCH bpf-next v7 4/5] selftests/bpf: Test " Kui-Feng Lee
2022-08-26 21:19 ` Yonghong Song
2022-08-26 21:24 ` Yonghong Song
2022-08-27 18:33 ` Kui-Feng Lee [this message]
2022-08-26 0:37 ` [PATCH bpf-next v7 5/5] bpftool: Show parameters of BPF task iterators Kui-Feng Lee
2022-08-26 11:23 ` Quentin Monnet
2022-08-26 22:58 ` Kui-Feng Lee
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=b453f23f1d78b40616e8d55649eed117a4925133.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