From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
mkl@pengutronix.de, mailhol.vincent@wanadoo.fr,
daniel@iogearbox.net, razor@blackwall.org, kuni1840@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH RESEND v3 net-next 00/10] rtnetlink: Convert rtnl_newlink() to per-netns RTNL.
Date: Tue, 12 Nov 2024 01:40:31 +0000 [thread overview]
Message-ID: <173137563151.43860.965503623477739139.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241108004823.29419-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 Nov 2024 16:48:13 -0800 you wrote:
> Patch 1 - 3 removes __rtnl_link_unregister and protect link_ops by
> its dedicated mutex to move synchronize_srcu() out of RTNL scope.
>
> Patch 4 introduces struct rtnl_nets and helper functions to acquire
> multiple per-netns RTNL in rtnl_newlink().
>
> Patch 5 - 8 are to prefetch the peer device's netns in rtnl_newlink().
>
> [...]
Here is the summary with links:
- [RESEND,v3,net-next,01/10] rtnetlink: Remove __rtnl_link_unregister().
https://git.kernel.org/netdev/net-next/c/d5ec8d91f82e
- [RESEND,v3,net-next,02/10] rtnetlink: Protect link_ops by mutex.
https://git.kernel.org/netdev/net-next/c/6b57ff21a310
- [RESEND,v3,net-next,03/10] rtnetlink: Remove __rtnl_link_register()
https://git.kernel.org/netdev/net-next/c/68297dbb967f
- [RESEND,v3,net-next,04/10] rtnetlink: Introduce struct rtnl_nets and helpers.
https://git.kernel.org/netdev/net-next/c/cbaaa6326bc5
- [RESEND,v3,net-next,05/10] rtnetlink: Add peer_type in struct rtnl_link_ops.
https://git.kernel.org/netdev/net-next/c/28690e5361c0
- [RESEND,v3,net-next,06/10] veth: Set VETH_INFO_PEER to veth_link_ops.peer_type.
https://git.kernel.org/netdev/net-next/c/0eb87b02a705
- [RESEND,v3,net-next,07/10] vxcan: Set VXCAN_INFO_PEER to vxcan_link_ops.peer_type.
https://git.kernel.org/netdev/net-next/c/6b84e558e95d
- [RESEND,v3,net-next,08/10] netkit: Set IFLA_NETKIT_PEER_INFO to netkit_link_ops.peer_type.
https://git.kernel.org/netdev/net-next/c/fefd5d082172
- [RESEND,v3,net-next,09/10] rtnetlink: Convert RTM_NEWLINK to per-netns RTNL.
https://git.kernel.org/netdev/net-next/c/d91191ffe23f
- [RESEND,v3,net-next,10/10] rtnetlink: Register rtnl_dellink() and rtnl_setlink() with RTNL_FLAG_DOIT_PERNET_WIP.
https://git.kernel.org/netdev/net-next/c/636af13f213b
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:[~2024-11-12 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 0:48 [PATCH RESEND v3 net-next 00/10] rtnetlink: Convert rtnl_newlink() to per-netns RTNL Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 01/10] rtnetlink: Remove __rtnl_link_unregister() Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 02/10] rtnetlink: Protect link_ops by mutex Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 03/10] rtnetlink: Remove __rtnl_link_register() Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 04/10] rtnetlink: Introduce struct rtnl_nets and helpers Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 05/10] rtnetlink: Add peer_type in struct rtnl_link_ops Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 06/10] veth: Set VETH_INFO_PEER to veth_link_ops.peer_type Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 07/10] vxcan: Set VXCAN_INFO_PEER to vxcan_link_ops.peer_type Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 08/10] netkit: Set IFLA_NETKIT_PEER_INFO to netkit_link_ops.peer_type Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 09/10] rtnetlink: Convert RTM_NEWLINK to per-netns RTNL Kuniyuki Iwashima
2024-11-08 0:48 ` [PATCH RESEND v3 net-next 10/10] rtnetlink: Register rtnl_dellink() and rtnl_setlink() with RTNL_FLAG_DOIT_PERNET_WIP Kuniyuki Iwashima
2024-11-12 1:40 ` 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=173137563151.43860.965503623477739139.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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;
as well as URLs for NNTP newsgroup(s).