Am Mittwoch 13 August 2008 21:34:30 schrieb Alan Stern:
quoted text
> On Wed, 13 Aug 2008, Oliver Neukum wrote:
> 
> > Am Mittwoch 13 August 2008 17:44:46 schrieb Alan Stern:
> > > > All children that are USB must be powered down. We know in fact that most
> > > > drives don't care that the device is suspended. The problem was drive
> > > > enclosures that cut power upon suspension losing cached data.
> > > 
> > > You misunderstood my question.  Are there SCSI transports other than
> > > USB sharing the requirement that all child devices must be suspended
> > > before the link can be powered down?
> > 
> > I dispute that USB in general has this property.
> 
> How can you dispute that?  You said it yourself, in the top quote
> above: "All children that are USB must be powered down."

But the children are SCSI, not USB.

quoted text
> > Some storage devices
> > need their caches flushed. USB itself is perfectly happy with autosuspending
> > the storage device (host) without telling the disks (devices)
> > 
> > You could even argue that these storage devices violate the USB spec.
> 
> Oliver, you can't have it both ways.  Either we do spin down disks and
> drain device caches before autosuspending usb-storage or we don't.

That is true.

quoted text
> For safety's sake, obviously we should.  The overhead is minimal since
> this happens only after the idle timeout has expired.  And for devices
> that don't support it (like flash storage), sd skips the spin-down
> command anway.

But you cannot make the conclusion that the ultimate children should have
any autosuspend attributes. We can implement autosuspend in usb storage
and propagate the suspend calls down the tree without SCSI knowing about
autosuspend.

Such a system would have it drawbacks, but it'd be a lot simpler.

	Regards
		Oliver
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/