From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
sdf@fomichev.me, netdev@vger.kernel.org, bpf@vger.kernel.org,
eric.dumazet@gmail.com, kuifeng@meta.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next] bpf: no longer acquire map_idr_lock in bpf_map_inc_not_zero()
Date: Mon, 03 Mar 2025 02:30:34 +0000 [thread overview]
Message-ID: <174096903429.3067520.8581639829502148937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250301191315.1532629-1-edumazet@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 1 Mar 2025 19:13:15 +0000 you wrote:
> bpf_sk_storage_clone() is the only caller of bpf_map_inc_not_zero()
> and is holding rcu_read_lock().
>
> map_idr_lock does not add any protection, just remove the cost
> for passive TCP flows.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Kui-Feng Lee <kuifeng@meta.com>
> Cc: Martin KaFai Lau <martin.lau@kernel.org>
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: no longer acquire map_idr_lock in bpf_map_inc_not_zero()
https://git.kernel.org/bpf/bpf-next/c/17a82ed98f62
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:[~2025-03-03 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 19:13 [PATCH bpf-next] bpf: no longer acquire map_idr_lock in bpf_map_inc_not_zero() Eric Dumazet
2025-03-02 0:05 ` Stanislav Fomichev
2025-03-03 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=174096903429.3067520.8581639829502148937.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.