From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Tejun Heo <tj@kernel.org>
Cc: Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211_hwsim: don't use WQ_MEM_RECLAIM
Date: Thu, 25 Jan 2018 22:01:26 +0100 [thread overview]
Message-ID: <1516914086.2189.9.camel@sipsolutions.net> (raw)
In-Reply-To: <5A6A3BFC.5090305@broadcom.com> (sfid-20180125_212019_075070_4A9FE925)
I guess we should just ask Tejun :-)
Tejun, the problem was a report that a WQ_MEM_RECLAIM workqueue is
flushing another that isn't, and it turns out that lots of wireless
drivers are using WQ_MEM_RECLAIM for some reason.
Arend said:
> > > > Maybe a hint in the documentation, that a work item on a WQ_MEM_RECLAIM
> > > > queue must not call flush of an !WQ_MEM_RECLAIM queue would be nice.
> > > > Maybe it's kind of obvious, but there is also a reminder not to forget
> > > > that flag, if a queue may have work items that reclaim memory
> > >
> > > Yeah, honestly, I'm not really sure either. Clearly we can't set it,
> > > but other drivers also set it...
> >
> > That triggered something in my memory. So indeed we use it in brcmfmac
> > as well. We used create_singlethread_workqueue(), but I wanted to avoid
> > snprintf and specify the name format so switched to using
> > alloc_ordered_workqueue() keeping WQ_MEM_RECLAIM as per the macro
> > definition.
>
> #define create_singlethread_workqueue(name) \
> alloc_ordered_workqueue("%s", __WQ_LEGACY | WQ_MEM_RECLAIM, name)
>
> > Don't recall why I dropped the __WQ_LEGACY flag though.
johannes
next prev parent reply other threads:[~2018-01-25 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 7:40 [PATCH v2] mac80211_hwsim: don't use WQ_MEM_RECLAIM Johannes Berg
2018-01-24 9:39 ` Benjamin Beichler
2018-01-24 10:46 ` Johannes Berg
[not found] ` <CAF7Mx6oASGjDrzVq4_t8Wt-DU7Zap1tcpz5vU7bk-Q5qzg4V=g@mail.gmail.com>
[not found] ` <CAF7Mx6o_Y0AeGQfhGKMkSxUHtRNyGaHh3g-TyvusJmsYyckFZg@mail.gmail.com>
[not found] ` <CAF7Mx6rg2XOOG0mZxnKiM_1ToB36Yc2A=sKQfN7drLsr3+4crw@mail.gmail.com>
2018-01-25 20:20 ` Arend van Spriel
2018-01-25 21:01 ` Johannes Berg [this message]
2018-01-25 22:26 ` Tejun Heo
2018-01-26 8:08 ` Johannes Berg
2018-01-26 15:05 ` Tejun Heo
2018-01-26 15:53 ` Benjamin Beichler
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=1516914086.2189.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Benjamin.Beichler@uni-rostock.de \
--cc=arend.vanspriel@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.