From: patchwork-bot+netdevbpf@kernel.org
To: Gyutae Bae <gyutae.opensource@navercorp.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, gyutae.bae@navercorp.com
Subject: Re: [PATCH] selftests/bpf: Add perfbuf multi-producer benchmark
Date: Tue, 20 Jan 2026 19:40:06 +0000 [thread overview]
Message-ID: <176893800636.583014.14681617112813663191.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120090716.82927-1-gyutae.opensource@navercorp.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 20 Jan 2026 18:07:16 +0900 you wrote:
> From: Gyutae Bae <gyutae.bae@navercorp.com>
>
> Add a multi-producer benchmark for perfbuf to complement the existing
> ringbuf multi-producer test. Unlike ringbuf which uses a shared buffer
> and experiences contention, perfbuf uses per-CPU buffers so the test
> measures scaling behavior rather than contention.
>
> [...]
Here is the summary with links:
- selftests/bpf: Add perfbuf multi-producer benchmark
https://git.kernel.org/bpf/bpf-next/c/2e6690d4f7fc
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-01-20 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:07 [PATCH] selftests/bpf: Add perfbuf multi-producer benchmark Gyutae Bae
2026-01-20 19:40 ` 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=176893800636.583014.14681617112813663191.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=gyutae.bae@navercorp.com \
--cc=gyutae.opensource@navercorp.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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