From: Tejun Heo <tj@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC PATCH v2 1/3] workqueue: support pausing ordered workqueues
Date: Wed, 10 May 2023 10:13:51 -1000 [thread overview]
Message-ID: <ZFv6_8rJxPid0gdd@slm.duckdns.org> (raw)
In-Reply-To: <20230510220918.1dc654070530.Ia49f779e11c2814294ea7f8bb29f825fb840be51@changeid>
On Wed, May 10, 2023 at 10:12:03PM +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Add some infrastructure to support pausing ordered
> workqueues, so that no work items are executing nor
> can execute while the workqueue is paused.
>
> This can be used to simplify locking between work
> structs and other processes (e.g. userspace calls)
> when the workqueue is paused while other code is
> running, where we can then more easily avoid issues
> in code paths needing to cancel works.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
I'd be happy to apply this once the rest of the patchset is ready.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-05-10 20:14 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 [this message]
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=ZFv6_8rJxPid0gdd@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).