From: Johannes Berg <johannes@sipsolutions.net>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [RFC PATCH v2 0/3] wifi locking simplification
Date: Wed, 10 May 2023 22:12:02 +0200 [thread overview]
Message-ID: <20230510201205.308542-1-johannes@sipsolutions.net> (raw)
The rationale etc. didn't change in v2, so see
https://lore.kernel.org/r/20230510160428.175409-1-johannes@sipsolutions.net
In v2 I dropped the workqueue locking patch and consequently
made new wiphy_work and wiphy_delayed_work things.
I kept the pause/resume for the workqueue because not that I
had it, it seemed simpler than keeping track of "should it be
paused" in a separate bool variable to not queue the work when
it shouldn't be ...
Still just serves to illustrate things, I didn't really test it.
johannes
next reply other threads:[~2023-05-10 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:12 Johannes Berg [this message]
2023-05-10 20:12 ` [RFC PATCH v2 1/3] workqueue: support pausing ordered workqueues Johannes Berg
2023-05-10 20:13 ` Tejun Heo
2023-05-10 20:12 ` [RFC PATCH v2 2/3] wifi: cfg80211: add a workqueue with special semantics Johannes Berg
2023-05-11 21:50 ` Johannes Berg
2023-05-10 20:12 ` [RFC PATCH v2 3/3] wifi: cfg80211: move scan done work to cfg80211 workqueue 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=20230510201205.308542-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®