public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Kui-Feng Lee <kuifeng@fb.com>
To: "quentin@isovalent.com" <quentin@isovalent.com>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	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>,
	Yonghong Song <yhs@fb.com>
Subject: Re: [PATCH bpf-next v7 5/5] bpftool: Show parameters of BPF task iterators.
Date: Fri, 26 Aug 2022 22:58:55 +0000	[thread overview]
Message-ID: <f7c9ba3e30218668baade2bcb142339943025172.camel@fb.com> (raw)
In-Reply-To: <c2de50b3-4928-4a7d-6028-fd04a1aeff00@isovalent.com>

On Fri, 2022-08-26 at 12:23 +0100, Quentin Monnet wrote:
> !-------------------------------------------------------------------|
>   This Message Is From an External Sender
> 
> > -------------------------------------------------------------------
> > !
> 
> On 26/08/2022 01:37, Kui-Feng Lee wrote:
> > Show tid or pid of iterators if giving an argument of tid or pid
> > 
> > For exampole, the commaned `bpftool link list` may list following
> 
> s/exampole/example/, s/commaned/command/
> 
> > 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 that belong to a process (pid) or a thread (tid).
> 
> s/that belong/those belonging/?
> 
> > 
> > Signed-off-by: Kui-Feng Lee <kuifeng@fb.com>
> > ---
> >  tools/bpf/bpftool/link.c | 19 +++++++++++++++++++
> >  1 file changed, 19 insertions(+)
> > 
> > diff --git a/tools/bpf/bpftool/link.c b/tools/bpf/bpftool/link.c
> > index 7a20931c3250..f96c18bb7a42 100644
> > --- a/tools/bpf/bpftool/link.c
> > +++ b/tools/bpf/bpftool/link.c
> > @@ -83,6 +83,13 @@ static bool is_iter_map_target(const char
> > *target_name)
> >                strcmp(target_name, "bpf_sk_storage_map") == 0;
> >  }
> >  
> > +static bool is_iter_task_target(const char *target_name)
> > +{
> > +       return strcmp(target_name, "task") == 0 ||
> > +               strcmp(target_name, "task_file") == 0 ||
> > +               strcmp(target_name, "task_vma") == 0;
> > +}
> > +
> >  static void show_iter_json(struct bpf_link_info *info,
> > json_writer_t *wtr)
> >  {
> >         const char *target_name = u64_to_ptr(info-
> > >iter.target_name);
> > @@ -91,6 +98,12 @@ static void show_iter_json(struct bpf_link_info
> > *info, json_writer_t *wtr)
> >  
> >         if (is_iter_map_target(target_name))
> >                 jsonw_uint_field(wtr, "map_id", info-
> > >iter.map.map_id);
> > +       else if (is_iter_task_target(target_name)) {
> > +               if (info->iter.task.tid)
> > +                       jsonw_uint_field(wtr, "tid", info-
> > >iter.task.tid);
> > +               if (info->iter.task.pid)
> > +                       jsonw_uint_field(wtr, "pid", info-
> > >iter.task.pid);
> > +       }
> >  }
> >  
> >  static int get_prog_info(int prog_id, struct bpf_prog_info *info)
> > @@ -208,6 +221,12 @@ static void show_iter_plain(struct
> > bpf_link_info *info)
> >  
> >         if (is_iter_map_target(target_name))
> >                 printf("map_id %u  ", info->iter.map.map_id);
> > +       else if (is_iter_task_target(target_name)) {
> > +               if (info->iter.task.tid)
> > +                       printf("tid %u ", info->iter.task.tid);
> > +               else if (info->iter.task.pid)
> > +                       printf("pid %u ", info->iter.task.pid);
> 
> Looks good, thanks! I note that you have an "if ... else ..." here,
> vs.
> two "if"s above for the JSON output. Could you please make this
> consistent?

Sure!


      reply	other threads:[~2022-08-26 22:59 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
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 [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=f7c9ba3e30218668baade2bcb142339943025172.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=quentin@isovalent.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