From: Tianyi Chen <hi@tychen.cc>
To: bpf@vger.kernel.org
Cc: qmo@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ihor.solodrai@linux.dev, linux-kselftest@vger.kernel.org,
daniel@iogearbox.net, ast@kernel.org, hi@tychen.cc
Subject: [PATCH bpf-next v7 0/2] bpftool: Batch hash map dumps with bounded buffers
Date: Wed, 04 Nov 2026 04:01:49 +0900 [thread overview]
Message-ID: <cover.1793732386.git.hi@tychen.cc> (raw)
Rebased on current bpf-next, retaining Quentin's Acked-by.
Changes in v7:
- Use the upstream error formatter for batch failures.
- Refresh the matched-base timings and syscall counts in patch 1.
The 12 batch tests and both upstream non-iterable-map tests pass on
x86-64 KVM with Linux 7.2.13 and 7.3.0. All 33 focused subtests also pass
with the map-info/recursive series; per-CPU fallback output is unchanged.
v6: https://lore.kernel.org/r/20260925174412.2028749-1-hi@tychen.cc
Tianyi Chen (2):
bpftool: Use batch lookups for hash map dumps
selftests/bpf: Check bpftool batch map dump contents
tools/bpf/bpftool/map.c | 123 ++++++++++-
.../bpf/prog_tests/bpftool_map_batch.c | 191 ++++++++++++++++++
2 files changed, 306 insertions(+), 8 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/bpftool_map_batch.c
base-commit: cd5bc55288d4fd999595c8f2af6a5408cbe92a52
--
2.56.0
next reply other threads:[~2026-11-03 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 19:01 Tianyi Chen [this message]
2026-11-03 19:01 ` [PATCH bpf-next v7 1/2] bpftool: Use batch lookups for hash map dumps Tianyi Chen
2026-11-04 2:26 ` Alexei Starovoitov
2026-11-03 19:01 ` [PATCH bpf-next v7 2/2] selftests/bpf: Check bpftool batch map dump contents 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.1793732386.git.hi@tychen.cc \
--to=hi@tychen.cc \
--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 \
/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