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,
	eddyz87@gmail.com, song@kernel.org, haoluo@google.com,
	yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@fomichev.me, jolsa@kernel.org,
	john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [RESEND][PATCH bpf-next] bpf: Check map->record at the beginning of check_and_free_fields()
Date: Sat, 15 Mar 2025 19:10:30 +0000	[thread overview]
Message-ID: <174206583052.2636935.6848646987775209104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250315150930.1511727-1-houtao@huaweicloud.com>

Hello:

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

On Sat, 15 Mar 2025 23:09:30 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> When there are no special fields in the map value, there is no need to
> invoke bpf_obj_free_fields(). Therefore, checking the validity of
> map->record in advance.
> 
> After the change, the benchmark result of the per-cpu update case in
> map_perf_test increased by 40% under a 16-CPU VM.
> 
> [...]

Here is the summary with links:
  - [RESEND,bpf-next] bpf: Check map->record at the beginning of check_and_free_fields()
    https://git.kernel.org/bpf/bpf-next/c/bb2243f4328b

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



      parent reply	other threads:[~2025-03-15 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 15:09 [RESEND][PATCH bpf-next] bpf: Check map->record at the beginning of check_and_free_fields() Hou Tao
2025-03-15 15:26 ` Kumar Kartikeya Dwivedi
2025-03-15 19: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=174206583052.2636935.6848646987775209104.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@fomichev.me \
    --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