From: patchwork-bot+netdevbpf@kernel.org
To: Hui Su <sh_def@163.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, leon.hwang@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v2] bpf: fix percpu map update indexing with sparse CPU IDs
Date: Fri, 21 Aug 2026 17:50:07 +0000 [thread overview]
Message-ID: <178733460765.1412990.8574022020312732917.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813155131.1022745-3-sh_def@163.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 13 Aug 2026 23:51:33 +0800 you wrote:
> Per-CPU array, hash, and cgroup storage map updates without BPF_F_CPU
> or BPF_F_ALL_CPUS use a value buffer whose per-CPU slots are packed in
> possible-CPU order. The buffer is sized as:
>
> round_up(value_size, 8) * num_possible_cpus()
>
> The update paths iterate over possible CPUs, but use the logical CPU ID
> to calculate the source offset:
>
> [...]
Here is the summary with links:
- [bpf,v2] bpf: fix percpu map update indexing with sparse CPU IDs
https://git.kernel.org/bpf/bpf/c/75b0a6db4300
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:[~2026-08-21 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:51 [PATCH bpf v2] bpf: fix percpu map update indexing with sparse CPU IDs Hui Su
2026-08-21 17:50 ` 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=178733460765.1412990.8574022020312732917.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=jolsa@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sh_def@163.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