From: Tianyi Chen <hi@tychen.cc>
To: bpf@vger.kernel.org
Cc: Tianyi Chen <hi@tychen.cc>,
qmo@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ihor.solodrai@linux.dev, linux-kselftest@vger.kernel.org,
shuah@kernel.org, daniel@iogearbox.net, ast@kernel.org,
alexei.starovoitov@gmail.com
Subject: [PATCH bpf-next v8 0/2] bpftool: Use batch lookups for map dumps
Date: Thu, 5 Nov 2026 03:55:02 +0900 [thread overview]
Message-ID: <cover.1793818387.git.hi@tychen.cc> (raw)
Use batch lookups for map dumps and continue with individual lookups
from the last printed key after any batch error.
Changes in v8:
- Follow Alexei's simpler approach: use a 1 MiB buffer budget, remove
buffer growth and error classes, and try batching for all map types.
- Count and fail bpftool's lookups in the selftest. Check plain and JSON
output, including failures before and after the first batch.
- Drop Quentin's Acked-by on the rewritten patch.
Tested in an x86-64 VM: all 16 batch subtests pass; unpatched bpftool
fails all 16. The combination with the recursive series also passes.
v7: https://lore.kernel.org/r/cover.1793732386.git.hi@tychen.cc
Tianyi Chen (2):
bpftool: Use batch lookups for map dumps
selftests/bpf: Check bpftool batch map dumps
tools/bpf/bpftool/map.c | 97 ++++++--
.../bpf/prog_tests/bpftool_map_batch.c | 228 ++++++++++++++++++
.../selftests/bpf/progs/bpftool_map_batch.c | 42 ++++
3 files changed, 352 insertions(+), 15 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/bpftool_map_batch.c
create mode 100644 tools/testing/selftests/bpf/progs/bpftool_map_batch.c
base-commit: 8fb43ffc3327d12d57d3fbe6f4820b5a522de0d1
--
2.56.0
next reply other threads:[~2026-11-04 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:55 Tianyi Chen [this message]
2026-11-04 18:55 ` [PATCH bpf-next v8 1/2] bpftool: Use batch lookups for map dumps Tianyi Chen
2026-11-04 18:55 ` [PATCH bpf-next v8 2/2] selftests/bpf: Check bpftool batch " Tianyi Chen
2026-11-04 19:21 ` sashiko-bot
2026-11-04 19:54 ` Tianyi Chen
2026-11-04 19:24 ` bot+bpf-ci
2026-11-04 19:54 ` Tianyi Chen
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=cover.1793818387.git.hi@tychen.cc \
--to=hi@tychen.cc \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=shuah@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 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.