From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: 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,
tj@kernel.org, void@manifault.com, bpf@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 0/5] bpf: Add bpf_iter_cpumask
Date: Wed, 7 Feb 2024 16:18:41 -0800 [thread overview]
Message-ID: <CAEf4Bzanbs0dO1jvisuw4X1zk-6P0YRZO2sLAtXaCLuaZKpnxw@mail.gmail.com> (raw)
In-Reply-To: <20240206081416.26242-1-laoar.shao@gmail.com>
On Tue, Feb 6, 2024 at 12:14 AM Yafang Shao <laoar.shao@gmail.com> wrote:
>
> Three new kfuncs, namely bpf_iter_cpumask_{new,next,destroy}, have been
> added for the new bpf_iter_cpumask functionality. These kfuncs enable the
> iteration of percpu data, such as runqueues, system_group_pcpu, and more.
>
> In our specific use case, we leverage the cgroup iterator to traverse
> percpu data, subsequently exposing it to userspace through a seq file.
> Refer to example in patch #2 for the usage.
>
> Changes:
> - v5 -> v6:
> - Various improvements on the comments (Andrii)
> - Use a static function instead as Kumar's patch[0] has been merged.
> (Anrii, Yonghong)
>
> [0]. https://lore.kernel.org/bpf/170719262630.31872.2248639771567354367.git-patchwork-notify@kernel.org
>
> - v4 -> v5:
> - Use cpumask_size() instead of sizeof(struct cpumask) (David)
> - Refactor the selftests as suggsted by David
> - Improve the doc as suggested by David
> - v3 -> v4:
> - Use a copy of cpumask to avoid potential use-after-free (Yonghong)
> - Various code improvement in selftests (Yonghong)
> - v2 -> v3:
> - Define KF_RCU_PROTECTED for bpf_iter_cpumask_new (Alexei)
> - Code improvement in selftests
> - Fix build error in selftest due to CONFIG_PSI=n
> reported by kernel test robot <lkp@intel.com>
> - v1 -> v2:
> - Avoid changing cgroup subsystem (Tejun)
> - Remove bpf_cpumask_set_from_pid(), and use bpf_cpumask_copy()
> instead (Tejun)
> - Use `int cpu;` field in bpf_iter_cpumask_kern (Andrii)
>
> Yafang Shao (5):
> bpf: Add bpf_iter_cpumask kfuncs
> bpf, docs: Add document for cpumask iter
> selftests/bpf: Fix error checking for cpumask_success__load()
> selftests/bpf: Mark cpumask kfunc declarations as __weak
I've applied patches 3 and 4, as they are general clean ups and
improvements independent from the actual iterator implementation.
Thanks!
> selftests/bpf: Add selftests for cpumask iter
>
> Documentation/bpf/cpumasks.rst | 60 +++++++
> kernel/bpf/cpumask.c | 79 +++++++++
> tools/testing/selftests/bpf/config | 1 +
> .../selftests/bpf/prog_tests/cpumask.c | 158 +++++++++++++++++-
> .../selftests/bpf/progs/cpumask_common.h | 60 +++----
> .../bpf/progs/cpumask_iter_failure.c | 99 +++++++++++
> .../bpf/progs/cpumask_iter_success.c | 126 ++++++++++++++
> 7 files changed, 552 insertions(+), 31 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/progs/cpumask_iter_failure.c
> create mode 100644 tools/testing/selftests/bpf/progs/cpumask_iter_success.c
>
> --
> 2.39.1
>
prev parent reply other threads:[~2024-02-08 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 8:14 [PATCH v6 bpf-next 0/5] bpf: Add bpf_iter_cpumask Yafang Shao
2024-02-06 8:14 ` [PATCH v6 bpf-next 1/5] bpf: Add bpf_iter_cpumask kfuncs Yafang Shao
2024-02-07 1:06 ` Alexei Starovoitov
2024-02-07 3:24 ` Yafang Shao
2024-02-06 8:14 ` [PATCH v6 bpf-next 2/5] bpf, docs: Add document for cpumask iter Yafang Shao
2024-02-06 8:14 ` [PATCH v6 bpf-next 3/5] selftests/bpf: Fix error checking for cpumask_success__load() Yafang Shao
2024-02-06 8:14 ` [PATCH v6 bpf-next 4/5] selftests/bpf: Mark cpumask kfunc declarations as __weak Yafang Shao
2024-02-06 15:48 ` Daniel Xu
2024-02-06 8:14 ` [PATCH v6 bpf-next 5/5] selftests/bpf: Add selftests for cpumask iter Yafang Shao
2024-02-08 0:18 ` Andrii Nakryiko [this message]
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=CAEf4Bzanbs0dO1jvisuw4X1zk-6P0YRZO2sLAtXaCLuaZKpnxw@mail.gmail.com \
--to=andrii.nakryiko@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=laoar.shao@gmail.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox