Drive behavior issue when START STOP unit forces drive to idle power condition

Penokie, George George.Penokie at lsi.com
Mon Jun 2 15:10:59 PDT 2008


* From the T10 Reflector (t10 at t10.org), posted by:
* "Penokie, George" <George.Penokie at lsi.com>
*
Gerry,
The ability to use the Start/Stop Unit command in cooperation with the Power
Condition mode page is already defined in the Start/Stop Unit command. The
Power Condition field codes Ah and Bh allow the application to force a change
to a different power condition without disabling the timers. In addition, if
the application does use the Start/Stop Unit command to control the power
conditions manually using Power Conditions 1h, 2h, or 3h it can switch over
to using the Power Condition mode page any time by issuing a Start/Stop Unit
command with the Power Condition set to 7h.
Bye for now,
George Penokie
LSI Corporation
3033 41st St. NW
Suite 100
Rochester, MN 55901
507-328-9017
george.penokie at lsi.com
-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of
Gerry.Houlder at seagate.com
Sent: Thursday, May 29, 2008 3:55 PM
To: t10 at t10.org
Subject: Drive behavior issue when START STOP unit forces drive to idle power
condition
* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*
While working on my additional idle power conditions proposal (08-184) I
encountered this issue with using START STOP UNIT command to force the drive
to idle mode.
Situation: initiator sends START STOP UNIT command that forces drive to idle
power condition. As defined today, this action disables any timers on the
Power Condition Mode page (page 0x1A) that happen to be enabled. Later a
media access command causes the drive to transition to active state to
process the command. Since the timers are disabled, the drive will stay in
active state until another START STOP UNIT command is sent.
Problem: With multi-initiator systems, will all the initiators know to send a
START STOP UNIT command to put the drive back to idle to conserve power?
If not, a drive that at least one initiator thinks is in an idle power
condition (conserving power) may actually be in active power condition for
long periods of time.
Possible solution: change the START STOP UNIT command behavior so that
sending the command causes the drive to transition immediately to the
requested power condition but don't disable the timers. Then if the drive
goes to active power condition to process a media access command, it will
still go to idle  power condition based on the timers. This would at least
limit the unnecessary active time of the drive to the values set in the
timers.
I'd like to hear what other companies think of this situation. Will drives
always be fully manged in a multi-initiator system so the stated problem will
not be an issue or should something be changed to limit the impact of this
issue? Are there existing implementations that use the current START STOP
UNIT behavior? If not, perhaps we can consider changing the behavior.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org



More information about the T10 mailing list