Alan Cox wrote:
Ar Maw, 2006-06-13 am 00:50 +0900, ysgrifennodd Tejun Heo:
Suspend is performed parallely on all ports of a host_set and resume
is done parallely in background to decrease the time necessary before
responding to user.
Do we need a disk count here - some large disk setups rely on the fact
drives don't all spin up at once to avoid overloading the PSU ?
For most desktops and notebooks, it doesn't really matter as power is
removed from disks during memsleep and they all spin up immediately
after resume regardless of what libata does. For external enclosures
with separate power supply, limiting the number of concurrent spinups
during resume is necessary though.
I think we need to make a central disk spinup limiter to control the
number of concurrent spinups across both ATA and SCSI. SATA staggered
spinup should be considered too. Depending on situation, a drive may
spin up on power up, PHY ready or IDLE_IMM after resuming from memsleep.
FWIW, my cheapo 325w PSU (< 30USD) hasn't had any problem spinning up 11
drives simultaneously.
I think it's okay to leave it as it is for the time being. It's not
like people w/ external enclosures use suspend/resume a lot.
--
tejun
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
