From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, rcu@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, paulmck@kernel.org,
kafai@fb.com, edumazet@google.com, kernel-team@fb.com
Subject: Re: [PATCH v4 bpf-next] selftests/bpf: Add benchmark for local_storage RCU Tasks Trace usage
Date: Thu, 07 Jul 2022 14:40:13 +0000 [thread overview]
Message-ID: <165720481360.13867.14770965317150614583.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220705190018.3239050-1-davemarchevsky@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 5 Jul 2022 12:00:18 -0700 you wrote:
> This benchmark measures grace period latency and kthread cpu usage of
> RCU Tasks Trace when many processes are creating/deleting BPF
> local_storage. Intent here is to quantify improvement on these metrics
> after Paul's recent RCU Tasks patches [0].
>
> Specifically, fork 15k tasks which call a bpf prog that creates/destroys
> task local_storage and sleep in a loop, resulting in many
> call_rcu_tasks_trace calls.
>
> [...]
Here is the summary with links:
- [v4,bpf-next] selftests/bpf: Add benchmark for local_storage RCU Tasks Trace usage
https://git.kernel.org/bpf/bpf-next/c/2b4b2621fd64
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:[~2022-07-07 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:00 [PATCH v4 bpf-next] selftests/bpf: Add benchmark for local_storage RCU Tasks Trace usage Dave Marchevsky
2022-07-07 14: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=165720481360.13867.14770965317150614583.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=davemarchevsky@fb.com \
--cc=edumazet@google.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
/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