From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <n05ec@lzu.edu.cn>
Cc: netdev@vger.kernel.org, horms@kernel.org, edumazet@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, kees@kernel.org, yuantan098@gmail.com,
ylong030@ucr.edu, yifanwucs@gmail.com, tomapufckgml@gmail.com,
bird@lzu.edu.cn
Subject: Re: [PATCH net v2 1/2] 8021q: use RCU for egress QoS mappings
Date: Thu, 23 Apr 2026 10:20:07 +0000 [thread overview]
Message-ID: <177693960705.95198.14343810737478655925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9136768189f8c6d3f824f476c62d2fa1111688e8.1776647968.git.yuantan098@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 20 Apr 2026 11:18:45 +0800 you wrote:
> From: Longxuan Yu <ylong030@ucr.edu>
>
> The TX fast path and reporting paths walk egress QoS mappings without
> RTNL. Convert the mapping lists to RCU-protected pointers, use RCU
> reader annotations in readers, and defer freeing mapping nodes with an
> embedded rcu_head.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] 8021q: use RCU for egress QoS mappings
https://git.kernel.org/netdev/net/c/fc69decc811b
- [net,v2,2/2] 8021q: delete cleared egress QoS mappings
https://git.kernel.org/netdev/net/c/7dddc74af369
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-04-23 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 3:18 [PATCH net v2 1/2] 8021q: use RCU for egress QoS mappings Ren Wei
2026-04-20 3:18 ` [PATCH net v2 2/2] 8021q: delete cleared " Ren Wei
2026-04-22 16:20 ` Simon Horman
2026-04-23 10:13 ` Paolo Abeni
2026-04-23 10: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=177693960705.95198.14343810737478655925.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bird@lzu.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=ylong030@ucr.edu \
--cc=yuantan098@gmail.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