From: patchwork-bot+netdevbpf@kernel.org
To: Qiliang Yuan <realwujing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, brauner@kernel.org, kuniyu@google.com,
jack@suse.cz, jlayton@kernel.org, yuanql9@chinatelecom.cn,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] netns: optimize netns cleaning by batching unhash_nsid calls
Date: Sat, 07 Feb 2026 04:20:22 +0000 [thread overview]
Message-ID: <177043802282.1183264.13017146634925007603.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204074854.3506916-1-realwujing@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Feb 2026 02:48:42 -0500 you wrote:
> Currently, unhash_nsid() scans the entire system for each netns being
> killed, leading to O(M_dying_net * N_alive_net * N_id) complexity, as
> __peernet2id() also performs a linear search in the IDR.
>
> Optimize this to O(N_alive_net * N_id) by batching unhash operations. Move
> unhash_nsid() out of the per-netns loop in cleanup_net() to perform a
> single-pass traversal over survivor namespaces.
>
> [...]
Here is the summary with links:
- [v6] netns: optimize netns cleaning by batching unhash_nsid calls
https://git.kernel.org/netdev/net-next/c/7acee67a6bce
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-02-07 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 7:48 [PATCH v6] netns: optimize netns cleaning by batching unhash_nsid calls Qiliang Yuan
2026-02-05 7:56 ` Kuniyuki Iwashima
2026-02-07 4: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=177043802282.1183264.13017146634925007603.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=realwujing@gmail.com \
--cc=yuanql9@chinatelecom.cn \
/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