From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Kuniyuki Iwashima <kuniyu@google.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-next-2026-10-07
Date: Wed, 7 Oct 2026 16:36:16 -0700 [thread overview]
Message-ID: <20261007163616.1088d364@kernel.org> (raw)
In-Reply-To: <20261007205827.467974-3-johannes@sipsolutions.net>
On Wed, 7 Oct 2026 22:57:00 +0200 Johannes Berg wrote:
> Nothing much going on in wireless-next. However, next time
> I hope to land my RTNL-redux series which will (almost)
> completely wean the wireless stack off the RTNL, except in
> places where we need it for netdev register/unregister/etc.
>
> I need to see what's going on with the per-netns mutex now,
> can we already use that instead?
That's a Kuniyuki question (cced). I've been trying to move
HW drivers out of rtnl_lock and under netdev->lock.
Most of the rtnl_lock contention I've seen in prod at Meta
is in init_net
next prev parent reply other threads:[~2026-10-07 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 20:57 [GIT PULL] wireless-next-2026-10-07 Johannes Berg
2026-10-07 23:36 ` Jakub Kicinski [this message]
2026-10-08 2:05 ` Kuniyuki Iwashima
2026-10-08 7:44 ` Johannes Berg
2026-10-08 15:01 ` Johannes Berg
2026-10-09 21:24 ` Kuniyuki Iwashima
2026-10-07 23:40 ` patchwork-bot+netdevbpf
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=20261007163616.1088d364@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuniyu@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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