From: Yonghong Song <yhs@fb.com>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>
Subject: [PATCH bpf-next v2 0/2] bpf: change uapi for bpf iterator map elements
Date: Mon, 3 Aug 2020 00:33:26 -0700 [thread overview]
Message-ID: <20200803073326.3745149-1-yhs@fb.com> (raw)
Andrii raised a concern that current uapi for bpf iterator map
element is a little restrictive and not suitable for future potential
complex customization. This is a valid suggestion, considering people
may indeed add more complex custimization to the iterator, e.g.,
cgroup_id + user_id, etc. for task or task_file. Another example might
be map_id plus additional control so that the bpf iterator may bail
out a bucket earlier if a bucket has too many elements which may hold
lock too long and impact other parts of systems.
Patch #1 modified uapi with kernel changes. Patch #2
adjusted libbpf api accordingly.
Changelogs:
v1 -> v2:
. ensure link_create target_fd/flags == 0 since they are not used. (Andrii)
. if either of iter_info ptr == 0 or iter_info_len == 0, but not both,
return error to user space. (Andrii)
. do not reject iter_info.map.map_fd == 0, go ahead to use it trying to
get a map reference since the map_fd is required for map_elem iterator.
. use bpf_iter_link_info in bpf_iter_attach_opts instead of map_fd.
this way, user space is responsible to set up bpf_iter_link_info and
libbpf just passes the data to the kernel, simplifying libbpf design.
(Andrii)
Yonghong Song (2):
bpf: change uapi for bpf iterator map elements
tools/bpf: support new uapi for map element bpf iterator
include/linux/bpf.h | 10 ++--
include/uapi/linux/bpf.h | 15 ++---
kernel/bpf/bpf_iter.c | 58 +++++++++----------
kernel/bpf/map_iter.c | 34 ++++++++---
kernel/bpf/syscall.c | 2 +-
net/core/bpf_sk_storage.c | 34 ++++++++---
tools/bpf/bpftool/iter.c | 8 ++-
tools/include/uapi/linux/bpf.h | 15 ++---
tools/lib/bpf/bpf.c | 3 +
tools/lib/bpf/bpf.h | 4 +-
tools/lib/bpf/libbpf.c | 6 +-
tools/lib/bpf/libbpf.h | 4 +-
.../selftests/bpf/prog_tests/bpf_iter.c | 34 ++++++++---
13 files changed, 146 insertions(+), 81 deletions(-)
--
2.24.1
next reply other threads:[~2020-08-03 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 7:33 Yonghong Song [this message]
2020-08-03 7:33 ` [PATCH bpf-next v2 1/2] bpf: change uapi for bpf iterator map elements Yonghong Song
2020-08-03 7:33 ` [PATCH bpf-next v2 2/2] tools/bpf: support new uapi for map element bpf iterator Yonghong Song
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=20200803073326.3745149-1-yhs@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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