BPF List
 help / color / mirror / Atom feed
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, yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
	john.fastabend@gmail.com, eddyz87@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3 0/3] bpf: inline bpf_kptr_xchg()
Date: Fri, 12 Jan 2024 02:30:27 +0000	[thread overview]
Message-ID: <170502662783.8539.15888768654431912677.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240105104819.3916743-1-houtao@huaweicloud.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri,  5 Jan 2024 18:48:16 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The motivation of inlining bpf_kptr_xchg() comes from the performance
> profiling of bpf memory allocator benchmark [1]. The benchmark uses
> bpf_kptr_xchg() to stash the allocated objects and to pop the stashed
> objects for free. After inling bpf_kptr_xchg(), the performance for
> object free on 8-CPUs VM increases about 2%~10%. However the performance
> gain comes with costs: both the kasan and kcsan checks on the pointer
> will be unavailable. Initially the inline is implemented in do_jit() for
> x86-64 directly, but I think it will more portable to implement the
> inline in verifier.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/3] bpf: Support inlining bpf_kptr_xchg() helper
    https://git.kernel.org/bpf/bpf-next/c/ac780beba187
  - [bpf-next,v3,2/3] selftests/bpf: Factor out get_xlated_program() helper
    https://git.kernel.org/bpf/bpf-next/c/10cdab919df6
  - [bpf-next,v3,3/3] selftests/bpf: Test the inlining of bpf_kptr_xchg()
    https://git.kernel.org/bpf/bpf-next/c/ca8cf57c7754

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-12  2:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 10:48 [PATCH bpf-next v3 0/3] bpf: inline bpf_kptr_xchg() Hou Tao
2024-01-05 10:48 ` [PATCH bpf-next v3 1/3] bpf: Support inlining bpf_kptr_xchg() helper Hou Tao
2024-01-05 10:48 ` [PATCH bpf-next v3 2/3] selftests/bpf: Factor out get_xlated_program() helper Hou Tao
2024-01-05 10:48 ` [PATCH bpf-next v3 3/3] selftests/bpf: Test the inlining of bpf_kptr_xchg() Hou Tao
2024-01-05 13:26   ` Eduard Zingerman
2024-01-06  2:32     ` Hou Tao
2024-01-05 22:53 ` [PATCH bpf-next v3 0/3] bpf: inline bpf_kptr_xchg() Song Liu
2024-01-06  2:34   ` Hou Tao
2024-01-06  8:51     ` Song Liu
2024-01-12  2:30 ` 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=170502662783.8539.15888768654431912677.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=eddyz87@gmail.com \
    --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=sdf@google.com \
    --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