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, eric.dumazet@gmail.com,
wenjia@linux.ibm.com, jaka@linux.ibm.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com
Subject: Re: [PATCH net-next] net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list()
Date: Tue, 05 Mar 2024 15:00:29 +0000 [thread overview]
Message-ID: <170965082961.24565.6815593821638612855.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240302100744.3868021-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 2 Mar 2024 10:07:44 +0000 you wrote:
> Many syzbot reports show extreme rtnl pressure, and many of them hint
> that smc acquires rtnl in netns creation for no good reason [1]
>
> This patch returns early from smc_pnet_net_init()
> if there is no netdevice yet.
>
> I am not even sure why smc_pnet_create_pnetids_list() even exists,
> because smc_pnet_netdev_event() is also calling
> smc_pnet_add_base_pnetid() when handling NETDEV_UP event.
>
> [...]
Here is the summary with links:
- [net-next] net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list()
https://git.kernel.org/netdev/net-next/c/00af2aa93b76
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-03-05 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 10:07 [PATCH net-next] net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() Eric Dumazet
2024-03-04 10:05 ` Wenjia Zhang
2024-03-05 15:00 ` 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=170965082961.24565.6815593821638612855.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).