Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Yonghong Song <yhs@fb.com>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next v4 0/3] bpf: implement link_query for bpf iterators
Date: Fri, 21 Aug 2020 14:17:16 -0700 [thread overview]
Message-ID: <CAADnVQ+6avUVgC422WWe_1aN_qLNiWKdOzGi7XSVm0M5dqjEvQ@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzZQOz_uBkSOSXRXvc2nb0y5FUvT7x_SWwCbgwzwQKVdBg@mail.gmail.com>
On Fri, Aug 21, 2020 at 12:04 PM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
>
> On Fri, Aug 21, 2020 at 11:44 AM Yonghong Song <yhs@fb.com> wrote:
> >
> > "link" has been an important concept for bpf ecosystem to connect
> > bpf program with other properties. Currently, the information related
> > information can be queried from userspace through bpf command
> > BPF_LINK_GET_NEXT_ID, BPF_LINK_GET_FD_BY_ID and BPF_OBJ_GET_INFO_BY_FD.
> > The information is also available by "cating" /proc/<pid>/fdinfo/<link_fd>.
> > Raw_tracepoint, tracing, cgroup, netns and xdp links are already
> > supported in the kernel and bpftool.
> >
> > This patch added support for bpf iterator. Patch #1 added generic support
> > for link querying interface. Patch #2 implemented callback functions
> > for map element bpf iterators. Patch #3 added bpftool support.
> >
> > Changelogs:
> > v3 -> v4:
> > . return target specific link_info even if target_name buffer
> > is empty. (Andrii)
> > v2 -> v3:
> > . remove extra '\t' when fdinfo prints map_id to make parsing
> > consistent. (Andrii)
> > v1 -> v2:
> > . fix checkpatch.pl warnings. (Jakub)
> >
> > Yonghong Song (3):
> > bpf: implement link_query for bpf iterators
> > bpf: implement link_query callbacks in map element iterators
> > bpftool: implement link_query for bpf iterators
> >
> > include/linux/bpf.h | 10 ++++++
> > include/uapi/linux/bpf.h | 7 ++++
> > kernel/bpf/bpf_iter.c | 58 ++++++++++++++++++++++++++++++++++
> > kernel/bpf/map_iter.c | 15 +++++++++
> > net/core/bpf_sk_storage.c | 2 ++
> > tools/bpf/bpftool/link.c | 44 ++++++++++++++++++++++++--
> > tools/include/uapi/linux/bpf.h | 7 ++++
> > 7 files changed, 140 insertions(+), 3 deletions(-)
> >
> > --
> > 2.24.1
> >
>
> LGTM, thanks.
>
> Acked-by: Andrii Nakryiko <andriin@fb.com>
Applied. Thanks
prev parent reply other threads:[~2020-08-21 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 18:44 Yonghong Song
2020-08-21 18:44 ` [PATCH bpf-next v4 1/3] " Yonghong Song
2020-08-21 18:44 ` [PATCH bpf-next v4 2/3] bpf: implement link_query callbacks in map element iterators Yonghong Song
2020-08-21 18:44 ` [PATCH bpf-next v4 3/3] bpftool: implement link_query for bpf iterators Yonghong Song
2020-08-21 19:04 ` [PATCH bpf-next v4 0/3] bpf: " Andrii Nakryiko
2020-08-21 21:17 ` Alexei Starovoitov [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=CAADnVQ+6avUVgC422WWe_1aN_qLNiWKdOzGi7XSVm0M5dqjEvQ@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.com \
--subject='Re: [PATCH bpf-next v4 0/3] bpf: implement link_query for bpf iterators' \
/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
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).