From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, horms@kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net-next 0/5] net: reduce RTNL pressure in unregister_netdevice()
Date: Thu, 16 Jan 2025 03:30:45 +0000 [thread overview]
Message-ID: <173699824504.995574.8048482828230619557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250114205531.967841-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 14 Jan 2025 20:55:26 +0000 you wrote:
> One major source of RTNL contention resides in unregister_netdevice()
>
> Due to RCU protection of various network structures, and
> unregister_netdevice() being a synchronous function,
> it is calling potentially slow functions while holding RTNL.
>
> I think we can release RTNL in two points, so that three
> slow functions are called while RTNL can be used
> by other threads.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/5] net: expedite synchronize_net() for cleanup_net()
https://git.kernel.org/netdev/net-next/c/0734d7c3d93c
- [v3,net-next,2/5] net: no longer assume RTNL is held in flush_all_backlogs()
https://git.kernel.org/netdev/net-next/c/8a2b61e9e879
- [v3,net-next,3/5] net: no longer hold RTNL while calling flush_all_backlogs()
https://git.kernel.org/netdev/net-next/c/cfa579f66656
- [v3,net-next,4/5] net: reduce RTNL hold duration in unregister_netdevice_many_notify() (part 1)
https://git.kernel.org/netdev/net-next/c/ae646f1a0bb9
- [v3,net-next,5/5] net: reduce RTNL hold duration in unregister_netdevice_many_notify() (part 2)
https://git.kernel.org/netdev/net-next/c/83419b61d187
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-01-16 3:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 20:55 [PATCH v3 net-next 0/5] net: reduce RTNL pressure in unregister_netdevice() Eric Dumazet
2025-01-14 20:55 ` [PATCH v3 net-next 1/5] net: expedite synchronize_net() for cleanup_net() Eric Dumazet
2025-01-14 22:57 ` Jesse Brandeburg
2025-01-14 20:55 ` [PATCH v3 net-next 2/5] net: no longer assume RTNL is held in flush_all_backlogs() Eric Dumazet
2025-01-14 23:01 ` Jesse Brandeburg
2025-01-14 20:55 ` [PATCH v3 net-next 3/5] net: no longer hold RTNL while calling flush_all_backlogs() Eric Dumazet
2025-01-14 23:04 ` Jesse Brandeburg
2025-02-10 4:13 ` Kuniyuki Iwashima
2025-01-14 20:55 ` [PATCH v3 net-next 4/5] net: reduce RTNL hold duration in unregister_netdevice_many_notify() (part 1) Eric Dumazet
2025-01-14 23:05 ` Jesse Brandeburg
2025-01-14 20:55 ` [PATCH v3 net-next 5/5] net: reduce RTNL hold duration in unregister_netdevice_many_notify() (part 2) Eric Dumazet
2025-01-14 23:09 ` Jesse Brandeburg
2025-01-16 3: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=173699824504.995574.8048482828230619557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.