From: Yonghong Song <yhs@fb.com>
To: Kui-Feng Lee <kuifeng@fb.com>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v5 2/3] bpf: Handle bpf_link_info for the parameterized task BPF iterators.
Date: Sat, 13 Aug 2022 15:23:25 -0700 [thread overview]
Message-ID: <2bfa7fb6-3041-046c-541f-9ab9c57b1cc1@fb.com> (raw)
In-Reply-To: <20220811001654.1316689-3-kuifeng@fb.com>
On 8/10/22 5:16 PM, Kui-Feng Lee wrote:
> Add new fields to bpf_link_info that users can query it through
> bpf_obj_get_info_by_fd().
>
> Signed-off-by: Kui-Feng Lee <kuifeng@fb.com>
> ---
> include/uapi/linux/bpf.h | 4 ++++
> kernel/bpf/task_iter.c | 18 ++++++++++++++++++
> tools/include/uapi/linux/bpf.h | 4 ++++
> 3 files changed, 26 insertions(+)
>
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index 6328aca0cf5c..627a16981c90 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -6143,6 +6143,10 @@ struct bpf_link_info {
> struct {
> __u32 map_id;
> } map;
> + struct {
> + __u32 tid;
> + __u32 tgid;
pid/tgid or tid/pid?
> + } task;
Please use another union outside of struct { ... } map.
Please see cgroup_iter patch for details:
https://lore.kernel.org/bpf/20220812202802.3774257-2-haoluo@google.com/
> };
> } iter;
> struct {
> diff --git a/kernel/bpf/task_iter.c b/kernel/bpf/task_iter.c
> index f2e21efe075d..d392b46c6d19 100644
> --- a/kernel/bpf/task_iter.c
> +++ b/kernel/bpf/task_iter.c
> @@ -606,6 +606,21 @@ static const struct bpf_iter_seq_info task_seq_info = {
> .seq_priv_size = sizeof(struct bpf_iter_seq_task_info),
> };
>
> +static int bpf_iter_fill_link_info(const struct bpf_iter_aux_info *aux, struct bpf_link_info *info)
> +{
> + switch (aux->task.type) {
> + case BPF_TASK_ITER_TID:
> + info->iter.task.tid = aux->task.tid;
> + break;
> + case BPF_TASK_ITER_TGID:
> + info->iter.task.tgid = aux->task.tgid;
> + break;
> + default:
> + break;
> + }
> + return 0;
> +}
> +
> static struct bpf_iter_reg task_reg_info = {
> .target = "task",
> .attach_target = bpf_iter_attach_task,
> @@ -616,6 +631,7 @@ static struct bpf_iter_reg task_reg_info = {
> PTR_TO_BTF_ID_OR_NULL },
> },
> .seq_info = &task_seq_info,
> + .fill_link_info = bpf_iter_fill_link_info,
How about show_fdinfo?
> };
>
> static const struct bpf_iter_seq_info task_file_seq_info = {
> @@ -637,6 +653,7 @@ static struct bpf_iter_reg task_file_reg_info = {
> PTR_TO_BTF_ID_OR_NULL },
> },
> .seq_info = &task_file_seq_info,
> + .fill_link_info = bpf_iter_fill_link_info,
> };
>
> static const struct bpf_iter_seq_info task_vma_seq_info = {
> @@ -658,6 +675,7 @@ static struct bpf_iter_reg task_vma_reg_info = {
> PTR_TO_BTF_ID_OR_NULL },
> },
> .seq_info = &task_vma_seq_info,
> + .fill_link_info = bpf_iter_fill_link_info,
> };
>
[...]
next prev parent reply other threads:[~2022-08-13 22:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 0:16 [PATCH bpf-next v5 0/3] Parameterize task iterators Kui-Feng Lee
2022-08-11 0:16 ` [PATCH bpf-next v5 1/3] bpf: " Kui-Feng Lee
2022-08-13 22:17 ` Yonghong Song
2022-08-15 1:01 ` Alexei Starovoitov
2022-08-16 4:42 ` Andrii Nakryiko
2022-08-18 3:40 ` Yonghong Song
2022-08-16 5:25 ` Andrii Nakryiko
2022-08-18 4:31 ` Yonghong Song
2022-08-25 17:50 ` Andrii Nakryiko
2022-08-16 17:00 ` Kui-Feng Lee
2022-08-14 20:24 ` Jiri Olsa
2022-08-16 17:21 ` Kui-Feng Lee
2022-08-15 23:08 ` Hao Luo
2022-08-16 19:11 ` Kui-Feng Lee
2022-08-16 5:02 ` Andrii Nakryiko
2022-08-16 18:45 ` Kui-Feng Lee
2022-08-11 0:16 ` [PATCH bpf-next v5 2/3] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-08-13 22:23 ` Yonghong Song [this message]
2022-08-11 0:16 ` [PATCH bpf-next v5 3/3] selftests/bpf: Test " Kui-Feng Lee
2022-08-13 22:50 ` Yonghong Song
2022-08-18 17:24 ` Kui-Feng Lee
2022-08-16 5:15 ` Andrii Nakryiko
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=2bfa7fb6-3041-046c-541f-9ab9c57b1cc1@fb.com \
--to=yhs@fb.com \
--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 \
/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