From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next 0/6] bench: fast in-kernel triggering benchmarks
Date: Wed, 27 Mar 2024 22:10:33 +0000 [thread overview]
Message-ID: <171157743303.7147.9524380873313435641.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240326162151.3981687-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 26 Mar 2024 09:21:45 -0700 you wrote:
> Remove "legacy" triggering benchmarks which rely on syscalls (and thus syscall
> overhead is a noticeable part of benchmark, unfortunately). Replace them with
> faster versions that rely on triggering BPF programs in-kernel through another
> simple "driver" BPF program. See patch #2 with comparison results.
>
> raw_tp/tp/fmodret benchmarks required adding a simple kfunc in kernel to be
> able to trigger a simple tracepoint from BPF program (plus it is also allowed
> to be replaced by fmod_ret programs). This limits raw_tp/tp/fmodret benchmarks
> to new kernels only, but it keeps bench tool itself very portable and most of
> other benchmarks will still work on wide variety of kernels without the need
> to worry about building and deploying custom kernel module. See patches #5
> and #6 for details.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/6] selftests/bpf: rename and clean up userspace-triggered benchmarks
https://git.kernel.org/bpf/bpf-next/c/8f54386ea7ec
- [v2,bpf-next,2/6] selftests/bpf: add batched, mostly in-kernel BPF triggering benchmarks
https://git.kernel.org/bpf/bpf-next/c/e6c97e34ad7e
- [v2,bpf-next,3/6] selftests/bpf: remove syscall-driven benchs, keep syscall-count only
https://git.kernel.org/bpf/bpf-next/c/850860ee6712
- [v2,bpf-next,4/6] selftests/bpf: lazy-load trigger bench BPF programs
https://git.kernel.org/bpf/bpf-next/c/f328a70ab28b
- [v2,bpf-next,5/6] bpf: add bpf_modify_return_test_tp() kfunc triggering tracepoint
https://git.kernel.org/bpf/bpf-next/c/c55e25089eba
- [v2,bpf-next,6/6] selftests/bpf: add batched tp/raw_tp/fmodret tests
https://git.kernel.org/bpf/bpf-next/c/b1d5f62f825d
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:[~2024-03-27 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 16:21 [PATCH v2 bpf-next 0/6] bench: fast in-kernel triggering benchmarks Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 1/6] selftests/bpf: rename and clean up userspace-triggered benchmarks Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 2/6] selftests/bpf: add batched, mostly in-kernel BPF triggering benchmarks Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 3/6] selftests/bpf: remove syscall-driven benchs, keep syscall-count only Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 4/6] selftests/bpf: lazy-load trigger bench BPF programs Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 5/6] bpf: add bpf_modify_return_test_tp() kfunc triggering tracepoint Andrii Nakryiko
2024-03-26 16:21 ` [PATCH v2 bpf-next 6/6] selftests/bpf: add batched tp/raw_tp/fmodret tests Andrii Nakryiko
2024-03-27 22:10 ` 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=171157743303.7147.9524380873313435641.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=kernel-team@meta.com \
--cc=martin.lau@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