lkml.org 
[lkml]   [2012]   [Feb]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 0/5] scsi, sd, pm, request based runtime PM for scsi disk
On Sun, 12 Feb 2012, Oliver Neukum wrote:

> Yes, we can use the same heuristics as everywhere.
> command queued -> autopm_get
> command finished -> autopm_put
>
> but for the USB host adapter, not the sr device

I still don't fully understand. Are you suggesting that we use the
normal autosuspend timeout mechanism for the disk drive (for example,
spin down the disk if it hasn't been used for five minutes), and then
autosuspend a USB mass-storage device whenever its children are
suspended and no commands are in progress? (In fact, there can't be
any commands in progress if all the children are suspended.)

Or are you suggesting that we autosuspend a USB mass-storage device
between commands, regardless of the state of its children? Didn't we
discuss this approach a year or two ago and decide against it?

> > Furthermore, if you use active commands as the condition for
> > suspending, what do you do when the act of suspending causes a command
> > to be sent? It is necessary to distinguish between ordinary commands
> > and those that are PM-related.
>
> No. This problem goes away if you correctly make the distinction between
> host controller/storage device and the disk drive.
> You use the "active command standard" for the host controller.
> Then you need not care about the commands needed to suspend a disk drive.
> You cannot suspend the host controller while the disk drive is being suspended
> anyway, as the tree constraint prevents it.
>
> For the disk drive you just declare them busy restarting the timeout as a command
> goes down to the hardware. There is an interesting case about what you do if
> the generic layer wants to autosuspend an sr device which has a command queued.
> I propose we catch that case in sr_suspend() and return -EBUSY in
> the autosuspend with command in flight case.

The SCSI drivers don't know much about the request queue -- the block
layer manages it. That's another reason for handling this at the block
layer.

Is there some special reason you're talking about sr (the SCSI CD/DVD
driver) instead of sd (the SCSI disk driver)?

Alan Stern



\
 
 \ /
  Last update: 2012-02-13 02:45    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site