From: Tejun Heo <tj@kernel.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
Geliang Tang <geliangtang@163.com>,
"GeyslanG.Bem@Karyakshetra" <geyslan@gmail.com>,
Masanari Iida <standby24x7@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Hocko <MHocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Saurabh Karajgaonkar <skarajga@visteon.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC] usb: host: u132-hcd: Remove deprecated create_singlethread_workqueue
Date: Wed, 27 Jul 2016 14:00:47 -0400 [thread overview]
Message-ID: <20160727180047.GJ4144@mtj.duckdns.org> (raw)
In-Reply-To: <1469611796.2408.4.camel@suse.com>
Hello, Oliver.
On Wed, Jul 27, 2016 at 11:29:56AM +0200, Oliver Neukum wrote:
> On Wed, 2016-07-27 at 14:50 +0530, Bhaktipriya Shridhar wrote:
> > The workqueue "workqueue" has multiple workitems which may require
> > ordering. Hence, a dedicated ordered workqueue has been used.
> > Since the workqueue is not being used on a memory reclaim path,
> > WQ_MEM_RECLAIM has not been set.
>
> That is incorrect. The work queue is used by the HCD to handle
> TDs, which are parts of basic IO. The HCD in turn is used by
> usb-storage and uas, which are block drivers and those are obviously
> used on the memory reclaim path.
Hmm... I didn't know the whole USB stack could operate without
allocating memory. Does usb stack have mempools and stuff all the way
through?
Thanks.
--
tejun
next prev parent reply other threads:[~2016-07-27 18:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 9:20 Bhaktipriya Shridhar
2016-07-27 9:29 ` Oliver Neukum
2016-07-27 18:00 ` Tejun Heo [this message]
2016-07-27 18:54 ` Alan Stern
2016-07-27 19:23 ` Tejun Heo
2016-07-27 20:45 ` Alan Stern
2016-07-29 13:11 ` Tejun Heo
2016-08-01 13:50 ` Michal Hocko
2016-08-01 14:20 ` Tejun Heo
2016-08-01 18:00 ` Alan Stern
2016-08-01 18:28 ` Michal Hocko
2016-08-02 8:06 ` Oliver Neukum
2016-08-02 8:18 ` Michal Hocko
2016-08-02 10:03 ` Oliver Neukum
2016-08-02 11:34 ` Michal Hocko
2016-08-02 11:44 ` Oliver Neukum
2016-08-02 12:48 ` Michal Hocko
2016-08-02 13:29 ` Oliver Neukum
2016-08-02 19:02 ` Tejun Heo
2016-08-02 21:26 ` Michal Hocko
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=20160727180047.GJ4144@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=MHocko@suse.com \
--cc=bhaktipriya96@gmail.com \
--cc=geliangtang@163.com \
--cc=geyslan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=oneukum@suse.com \
--cc=skarajga@visteon.com \
--cc=standby24x7@gmail.com \
--cc=vbabka@suse.cz \
/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®