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: Re: [RFC PATCH v2 2/3] wifi: cfg80211: add a workqueue with special semantics
Date: Thu, 11 May 2023 23:50:35 +0200 [thread overview]
Message-ID: <aa7a0e08edf6567db027058cd331dfae86f54e62.camel@sipsolutions.net> (raw)
In-Reply-To: <20230510220918.96de601f45f6.I28a06f59bf647db6dea519e6fca1894f94227d73@changeid>
Now that I look at this more ...
> +static void cfg80211_wiphy_work(struct work_struct *work)
> +{
> + struct cfg80211_registered_device *rdev;
> +
> + rdev = container_of(work, struct cfg80211_registered_device, wiphy_work);
> +
> + spin_lock_irq(&rdev->wiphy_work_lock);
> + while (!list_empty(&rdev->wiphy_work_list)) {
> + struct wiphy_work *wk;
> +
> + wk = list_first_entry(&rdev->wiphy_work_list,
> + struct wiphy_work, entry);
> + list_del_init(&wk->entry);
> + spin_unlock_irq(&rdev->wiphy_work_lock);
> +
> + mutex_lock(&rdev->wiphy.mtx);
If I just change the locking here to take the wiphy.mtx before looking
at the list, which basically doesn't matter, then I don't even need
workqueue_pause() and all, nor do I even need a separate workqueue, just
schedule_work() will be good enough ... Just needs a _bit_ more work
when cancelling and here we should reschedule the work if the list isn't
empty after the first round, but overall that ends up far simpler.
So I think I'll drop the workqueue pause/resume the next time around,
FWIW.
johannes
next prev parent reply other threads:[~2023-05-11 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:12 [RFC PATCH v2 0/3] wifi locking simplification Johannes Berg
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 [this message]
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=aa7a0e08edf6567db027058cd331dfae86f54e62.camel@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®