lkml.org 
[lkml]   [2005]   [Sep]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: SATA suspend/resume (was Re: [PATCH] updated version of Jens' SATA suspend-to-ram patch)
I admit I haven't studied the patches. Anyway, here is what I have to 
say about what I (mis?)understood from your posts:

James Smart wrote:
> You need to be careful on the power-up. Many JBODs share a single
> "enclosure" and that enclosure has a limited power supply. If all
> drives were spun up in parallel (and a drive may take 10-15seconds
> to spin up), then they can overload the enclosure's power limit.
[...]
> There were not a lot of great answers on how to solve this as it usually
> required knowledge of how the hardware was packaged.
[...]

>>On Thu, Sep 29, 2005 at 08:34:37AM +0100, Christoph Hellwig wrote:
>>>is an ULDD operation, not an LLDD one, and this fits the layering model
>>>much better.

The operation _involves_ the high level, yes. But whether it may be/
must not be performed has to be controlled by the transport layer. Take
FireWire as an example: IEEE 1394(a,b) has power management
specifications. (NB: Its indeed in IEEE 1394, not in the SBP-2 spec.)
One rule is that only one node on a FireWire bus may perform power
management; the node which is allowed to do this is determined by a
special protocol.

>>Actually one important thing is missing, that is a way to avoid spinning
>>down external disks. As a start a sysfs-controlable flag should do it,
>>later we can add transport-specific ways to find out whether a device
>>is external.

It is not a question of external vs. internal, at least not if you
consider more than SATA. Power management is the genuine task of
transport layers (specifically, of transport management layers). These
layers might need assistence from SCSI high-level protocol layer though.

IOW it's certainly correct to provide suspend/resume helpers in SCSI
high level (probably abstracted through SCSI core), but whether these
helpers are called or not has to be decided down in the SCSI low level,
or even further beneath that level.
--
Stefan Richter
-=====-=-=-= =--= ===-=
http://arcgraph.de/sr/
-
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/

\
 
 \ /
  Last update: 2005-09-29 18:00    [W:0.030 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site