mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Fushuai Wang <wangfushuai@baidu.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, ast@kernel.org,
	martin.lau@kernel.org, houtao1@huawei.com, jkangas@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, menglong.dong@linux.dev
Subject: Re: [PATCH v2] bpf: Use rcu_read_lock_dont_migrate in bpf_sk_storage.c
Date: Tue, 07 Oct 2025 20:50:05 +0000	[thread overview]
Message-ID: <175987020501.2779563.3748034053990134861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251007074011.12916-1-wangfushuai@baidu.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Tue, 7 Oct 2025 15:40:11 +0800 you wrote:
> Use rcu_read_lock_dont_migrate() and rcu_read_unlock_migrate() in
> bpf_sk_storage.c to obtain better performance when PREEMPT_RCU is
> not enabled.
> 
> Signed-off-by: Fushuai Wang <wangfushuai@baidu.com>
> ---
> v1 -> v2: no code changes. Simplify and clarify commit message
> 
> [...]

Here is the summary with links:
  - [v2] bpf: Use rcu_read_lock_dont_migrate in bpf_sk_storage.c
    https://git.kernel.org/bpf/bpf-next/c/0db4941d9dae

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



      reply	other threads:[~2025-10-07 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  7:40 Fushuai Wang
2025-10-07 20: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=175987020501.2779563.3748034053990134861.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=jkangas@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=menglong.dong@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wangfushuai@baidu.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

Powered by JetHome