From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yhs@fb.com, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, paulmck@kernel.org,
rcu@vger.kernel.org, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v9] selftests/bpf: Add benchmark for bpf memory allocator
Date: Thu, 06 Jul 2023 01:50:20 +0000 [thread overview]
Message-ID: <168860822054.22142.13852026022704379153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230704025039.938914-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 4 Jul 2023 10:50:39 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> The benchmark could be used to compare the performance of hash map
> operations and the memory usage between different flavors of bpf memory
> allocator (e.g., no bpf ma vs bpf ma vs reuse-after-gp bpf ma). It also
> could be used to check the performance improvement or the memory saving
> provided by optimization.
>
> [...]
Here is the summary with links:
- [bpf-next,v9] selftests/bpf: Add benchmark for bpf memory allocator
https://git.kernel.org/bpf/bpf-next/c/fd283ab196a8
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-07-06 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 2:50 [PATCH bpf-next v9] selftests/bpf: Add benchmark for bpf memory allocator Hou Tao
2023-07-06 1: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=168860822054.22142.13852026022704379153.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).