From: Florian Lehner <dev@der-flo.net>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, aspsk@isovalent.com, kees@kernel.org,
quic_abchauha@quicinc.com, martin.kelly@crowdstrike.com,
mykolal@fb.com, shuah@kernel.org, yikai.lin@vivo.com,
Florian Lehner <dev@der-flo.net>
Subject: [bpf-next 0/2] bpf: Add flag for batch operation
Date: Sun, 10 Nov 2024 12:29:02 +0100 [thread overview]
Message-ID: <20241110112905.64616-1-dev@der-flo.net> (raw)
Introduce a new flag for batch operations that allows the deletion process
to continue even if certain keys are missing. This simplifies map flushing
by eliminating the requirement to maintain a separate list of keys and
makes sure maps can be flushed with a single batch delete operation.
Florian Lehner (2):
bpf: Add flag to continue batch operation
selftests/bpf: Add a test for batch operation flag
include/uapi/linux/bpf.h | 5 +++++
kernel/bpf/syscall.c | 14 ++++++++++---
tools/include/uapi/linux/bpf.h | 5 +++++
.../bpf/map_tests/htab_map_batch_ops.c | 20 ++++++++++++++++++-
4 files changed, 40 insertions(+), 4 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-10 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 11:29 Florian Lehner [this message]
2024-11-10 11:29 ` [bpf-next 1/2] bpf: Add flag to continue batch operation Florian Lehner
2024-11-10 11:29 ` [bpf-next 2/2] selftests/bpf: Add a test for batch operation flag Florian Lehner
2024-11-11 14:15 ` [bpf-next 0/2] bpf: Add flag for batch operation Hou Tao
2024-11-12 3:01 ` Alexei Starovoitov
2024-11-12 19:13 ` dev
2024-11-12 19:47 ` Alexei Starovoitov
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=20241110112905.64616-1-dev@der-flo.net \
--to=dev@der-flo.net \
--cc=andrii@kernel.org \
--cc=aspsk@isovalent.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.kelly@crowdstrike.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=quic_abchauha@quicinc.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yikai.lin@vivo.com \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.