From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
yonghong.song@linux.dev, tj@kernel.org, memxor@gmail.com,
houtao@huaweicloud.com
Subject: Re: [PATCH v4 0/3] bpf: introduce helper for populating bpf_cpumask
Date: Thu, 06 Mar 2025 01:30:30 +0000 [thread overview]
Message-ID: <174122463076.1088218.16223857286520093233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250305211235.368399-1-emil@etsalapatis.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 5 Mar 2025 16:12:32 -0500 you wrote:
> Some BPF programs like scx schedulers have their own internal CPU mask types,
> mask types, which they must transform into struct bpf_cpumask instances
> before passing them to scheduling-related kfuncs. There is currently no
> way to efficiently populate the bitfield of a bpf_cpumask from BPF memory,
> and programs must use multiple bpf_cpumask_[set, clear] calls to do so.
> Introduce a kfunc helper to populate the bitfield of a bpf_cpumask from valid
> BPF memory with a single call.
>
> [...]
Here is the summary with links:
- [v4,1/3] bpf: add kfunc for populating cpumask bits
https://git.kernel.org/bpf/bpf-next/c/a6db20f88a63
- [v4,2/3] selftests: bpf: add bpf_cpumask_fill selftests
https://git.kernel.org/bpf/bpf-next/c/66be130f8bf9
- [v4,3/3] bpf: fix missing kdoc string fields in cpumask.c
https://git.kernel.org/bpf/bpf-next/c/f3839e9749b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-06 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 21:12 [PATCH v4 0/3] bpf: introduce helper for populating bpf_cpumask Emil Tsalapatis
2025-03-05 21:12 ` [PATCH v4 1/3] bpf: add kfunc for populating cpumask bits Emil Tsalapatis
2025-03-06 1:54 ` Hou Tao
2025-03-05 21:12 ` [PATCH v4 2/3] selftests: bpf: add bpf_cpumask_fill selftests Emil Tsalapatis
2025-03-06 1:56 ` Hou Tao
2025-03-06 2:20 ` Alexei Starovoitov
2025-03-06 2:36 ` Emil Tsalapatis
2025-03-06 6:59 ` Hou Tao
2025-03-05 21:12 ` [PATCH v4 3/3] bpf: fix missing kdoc string fields in cpumask.c Emil Tsalapatis
2025-03-06 1:30 ` patchwork-bot+netdevbpf [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=174122463076.1088218.16223857286520093233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=houtao@huaweicloud.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=tj@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