From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ath9k-devel@lists.ath9k.org,
Reinette Chatre <reinette.chatre@intel.com>,
Dan Williams <dcbw@redhat.com>,
Lennert Buytenhek <buytenh@marvell.com>,
Daniel Drake <ddrake@brontes3d.com>
Subject: Re: [PATCH] mac80211: redefine usage of the mac80211 workqueue
Date: Sat, 25 Jul 2009 10:35:09 +0200 [thread overview]
Message-ID: <1248510909.32151.48.camel@johannes.local> (raw)
In-Reply-To: <1248482853-17032-2-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Fri, 2009-07-24 at 20:47 -0400, Luis R. Rodriguez wrote:
> The mac80211 workqueue exists to enable mac80211 and drivers
> to queue their own work on a single threaded workqueue. mac80211
> takes care to flush the workqueue during suspend but we never
> really had requirements on drivers for how they should use
> the workqueue in consideration for suspend.
>
> We extend mac80211 to document how the mac80211 workqueue should
> be used, how it should not be used and finally move raw access to
> the workqueue to mac80211 only. Drivers and mac80211 use helpers
> to queue work and flush the mac80211 workqueue:
>
> * ieee80211_queue_work()
> * ieee80211_queue_delayed_work()
> * ieee80211_flush_workqueue()
I would prefer to have wait_on_work() and/or cancel_work_sync() instead
of flushing? It's often preferable due to locking constraints to
cancel_work_sync() instead of flush_workqueue(). Do people really need
flush_workqueue()?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-25 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 0:47 [PATCH] mac80211/drivers: add new mac80211 workqueue API Luis R. Rodriguez
2009-07-25 0:47 ` [PATCH] mac80211: redefine usage of the mac80211 workqueue Luis R. Rodriguez
2009-07-25 8:35 ` Johannes Berg [this message]
2009-07-26 8:06 ` Luis R. Rodriguez
2009-07-25 0:47 ` [PATCH] mac80211: do not queue work after suspend in the dynamic ps timer Luis R. Rodriguez
2009-07-27 15:37 ` Luis R. Rodriguez
2009-07-25 0:47 ` [PATCH] ath9k: cancel xmit poll work at stop() callback Luis R. Rodriguez
2009-07-26 9:48 ` Luis R. Rodriguez
2009-07-25 0:50 ` [PATCH] mac80211/drivers: add new mac80211 workqueue API Luis R. Rodriguez
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=1248510909.32151.48.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=buytenh@marvell.com \
--cc=dcbw@redhat.com \
--cc=ddrake@brontes3d.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=reinette.chatre@intel.com \
/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