From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [RFC PATCH v2 00/13] wifi: lock contention improvements
Date: Mon, 5 Oct 2026 12:06:16 +0200 [thread overview]
Message-ID: <20261005101057.1992330-15-johannes@sipsolutions.net> (raw)
As before, on top of the series I just sent:
https://lore.kernel.org/linux-wireless/20261005100525.1991059-20-johannes@sipsolutions.net/
The idea is the same: make some methods unlocked to avoid lock
contention on the wiphy mutex, adding also a new "update beacon"
method (but that needs driver opt-in, for iwlwifi that'd be ~40
lines changed since it can send commands async).
I've changed the approach though - in part to cover NAN TX, but
also to make it a bit more easier to reason about and extend in
the future for other wdevs.
So patch 5 is new, split out from what was patch 5 before and
is now patch 6, to make it easier to understand.
I'm actually pretty happy with this and it passes tests, so I
see no reason not to do this, but it won't apply on the tree
now and I need to settle the RTNL redux first, so still RFC.
johannes
next reply other threads:[~2026-10-05 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:06 Johannes Berg [this message]
2026-10-05 10:06 ` [RFC PATCH v2 01/13] wifi: mac80211: protect AP template pointers with a spinlock Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 02/13] wifi: nl80211: add NL80211_CMD_UPDATE_BEACON Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 03/13] wifi: mac80211: implement lockless beacon updates Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 04/13] wifi: mac80211_hwsim: support " Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 05/13] wifi: nl80211: prepare for unlocked wdev-only ops Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 06/13] wifi: nl80211: allow mgmt frame TX without wiphy mutex Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 07/13] wifi: cfg80211: make cookie counter atomic Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 08/13] wifi: mac80211: refactor mgmt frames TX Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 09/13] wifi: mac80211: implement mgmt_tx_unlocked() Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 10/13] wifi: mac80211: don't require wiphy mutex for probe_peer Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 11/13] wifi: nl80211: probe peers without wiphy mutex Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 12/13] wifi: mac80211: don't require wiphy mutex for control port TX Johannes Berg
2026-10-05 10:06 ` [RFC PATCH v2 13/13] wifi: nl80211: transmit control port frames without wiphy mutex Johannes Berg
2026-10-05 12:44 ` [RFC PATCH v2 00/13] wifi: lock contention improvements Johannes Berg
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=20261005101057.1992330-15-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@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