From: patchwork-bot+netdevbpf@kernel.org
To: Yipeng Zou <zouyipeng@huawei.com>
Cc: ast@kernel.org, daniel@iogearbox.ne, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org, toke@redhat.com
Subject: Re: [bpf-next] selftests/bpf: clean-up fmod_ret in bench_rename test script
Date: Mon, 14 Aug 2023 16:50:21 +0000 [thread overview]
Message-ID: <169203182167.3806.17645689182437041748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230814030727.3010390-1-zouyipeng@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 14 Aug 2023 11:07:27 +0800 you wrote:
> [root@localhost bpf]# ./benchs/run_bench_rename.sh
> base : 0.819 ± 0.012M/s
> kprobe : 0.538 ± 0.009M/s
> kretprobe : 0.503 ± 0.004M/s
> rawtp : 0.779 ± 0.020M/s
> fentry : 0.726 ± 0.007M/s
> fexit : 0.691 ± 0.007M/s
> benchmark 'rename-fmodret' not found
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: clean-up fmod_ret in bench_rename test script
https://git.kernel.org/bpf/bpf-next/c/83a89c4b6ae9
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:[~2023-08-14 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 3:07 [bpf-next] selftests/bpf: clean-up fmod_ret in bench_rename test script Yipeng Zou
2023-08-14 16: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=169203182167.3806.17645689182437041748.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.ne \
--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=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=toke@redhat.com \
--cc=yonghong.song@linux.dev \
--cc=zouyipeng@huawei.com \
/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