From: Yafang Shao <laoar.shao@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org
Cc: bpf@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH bpf-next 0/2] bpf: Add a generic bits iterator
Date: Sun, 18 Feb 2024 19:48:16 +0800 [thread overview]
Message-ID: <20240218114818.13585-1-laoar.shao@gmail.com> (raw)
Introducing three new kfuncs, namely bpf_iter_bits_{new,next,destroy}, to
support the newly added bits iter functionality. These functions enable
seamless iteration of bits from a specified memory area.
- bpf_iter_bits_new
Initializes a new bits iterator for a given memory area. Notably, due to
limitations within bpf memalloc, the maximum number of bits that can be
iterated over is constrained to (4096 * 8).
- bpf_iter_bits_next
Get the next bit in a bpf_iter_bits
- bpf_iter_bits_destroy
Destroy a bpf_iter_bits
The bits iterator can be used in any context and on any address.
In our specific use case, we leverage the cgroup iterator to traverse
percpu data, subsequently exposing it to userspace through a seq file.
For detailed usage examples, please refer to the example in patch #2.
Changes:
- bpf: Add bpf_iter_cpumask
https://lwn.net/Articles/961104/
- bpf: Add new bpf helper bpf_for_each_cpu
https://lwn.net/Articles/939939/
Yafang Shao (2):
bpf: Add bits iterator
selftests/bpf: Add selftest for bits iter
kernel/bpf/helpers.c | 100 ++++++++++
tools/testing/selftests/bpf/config | 1 +
.../selftests/bpf/prog_tests/bits_iter.c | 180 ++++++++++++++++++
.../bpf/progs/test_bits_iter_failure.c | 53 ++++++
.../bpf/progs/test_bits_iter_success.c | 146 ++++++++++++++
5 files changed, 480 insertions(+)
create mode 100644 tools/testing/selftests/bpf/prog_tests/bits_iter.c
create mode 100644 tools/testing/selftests/bpf/progs/test_bits_iter_failure.c
create mode 100644 tools/testing/selftests/bpf/progs/test_bits_iter_success.c
--
2.39.1
next reply other threads:[~2024-02-18 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 11:48 Yafang Shao [this message]
2024-02-18 11:48 ` [PATCH bpf-next 1/2] bpf: Add bits iterator Yafang Shao
2024-02-26 23:21 ` John Fastabend
2024-02-27 0:20 ` Alexei Starovoitov
2024-02-27 0:34 ` John Fastabend
2024-02-18 11:48 ` [PATCH bpf-next 2/2] selftests/bpf: Add selftest for bits iter Yafang Shao
2024-02-22 17:36 ` Alexei Starovoitov
2024-02-23 2:29 ` Yafang Shao
2024-02-23 11:52 ` Eduard Zingerman
2024-02-25 2:29 ` Yafang Shao
2024-02-25 19:38 ` kernel test robot
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=20240218114818.13585-1-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=andrii@kernel.org \
--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=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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 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).