From: patchwork-bot+netdevbpf@kernel.org
To: Qi Wu <shijing.wuqi@linux.alibaba.com>
Cc: daniel@iogearbox.net, ast@kernel.org, andrii@kernel.org,
razor@blackwall.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
martin.lau@linux.dev, john.fastabend@gmail.com, sdf@fomichev.me,
eddyz87@gmail.com, memxor@gmail.com, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
ihor.solodrai@linux.dev, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, davem@davemloft.net, andrew+netdev@lunn.ch
Subject: Re: [PATCH bpf-next v3] bpf, mprog: Defer RCU synchronization until peer reuse
Date: Tue, 17 Nov 2026 05:20:04 +0000 [thread overview]
Message-ID: <179489280438.347631.11158166869237958390.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116145318.34084-1-shijing.wuqi@linux.alibaba.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 16 Nov 2026 22:53:18 +0800 you wrote:
> bpf_mprog_attach() swaps the active entry and the caller then waits
> for a grace period (tcx_entry_sync() / netkit_entry_sync()) before
> returning. But attach releases nothing: the old entry only has to
> stay intact until the next attach or detach overwrites it as the
> peer. The unconditional wait buys nothing on the attach path, yet it
> runs inside rtnl_lock() and serializes the whole machine's network
> control plane. Creating containers in bulk pays 2N grace periods for
> N devices, one first attach per direction.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf, mprog: Defer RCU synchronization until peer reuse
https://git.kernel.org/bpf/bpf-next/c/32b66b94c86f
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:[~2026-11-17 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 14:53 [PATCH bpf-next v3] bpf, mprog: Defer RCU synchronization until peer reuse Qi Wu
2026-11-16 15:43 ` bot+bpf-ci
2026-11-17 5:20 ` 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=179489280438.347631.11158166869237958390.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@kernel.org \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=sdf@fomichev.me \
--cc=shijing.wuqi@linux.alibaba.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