From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH v3 3/6] uas: make work list per-device Date: Tue, 24 Sep 2013 01:52:27 -0700 Message-ID: <20130924085227.GF11858@infradead.org> References: <1379071635-30701-1-git-send-email-kraxel@redhat.com> <1379071635-30701-4-git-send-email-kraxel@redhat.com> <20130917203012.GA1752@infradead.org> <1379489584.12907.11.camel@nilsson.home.kraxel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1379489584.12907.11.camel@nilsson.home.kraxel.org> Sender: linux-kernel-owner@vger.kernel.org To: Gerd Hoffmann Cc: Christoph Hellwig , linux-usb@vger.kernel.org, Matthew Wilcox , Sarah Sharp , Matthew Dharm , Greg Kroah-Hartman , "open list:USB ATTACHED SCSI" , "open list:USB MASS STORAGE..." , open list List-Id: linux-scsi@vger.kernel.org On Wed, Sep 18, 2013 at 09:33:04AM +0200, Gerd Hoffmann wrote: > > > While being at it rename the list head from "list" to "work", preparing > > > for the addition of a second list. > > > > Why do you even the list? > > The list was already there when I took over maintainance ... > > > What would a ordered per-device workqueue not > > provide? > > Had no reason to look into replacing the list with something else so > far. Why do you suggest using a workqueue instead? > > Note that the list is not used in a typical request workflow. Only in > case queuing an usb urb failed the request is linked into the list and > the worker will try to submit the usb urb again. The driver is only using the list to queue up things into workqueue context as far as I can see. Which means it's far easier to leave that to the workqueue.