SCSI/ATA Translation of Command Duration Limit (T10/15-093)
Ralph.Weber at wdc.com
Wed Jun 10 17:42:52 PDT 2015
Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1506103_f.htm">HTML-formatted message</a>
As David Black would say at a time like this ... "With my chair's hat totally
Option b for times larger than 90 seconds and smaller than 1 millisecond
Option a for all other conversions
All the best,
From: owner-t10 at t10.org [owner-t10 at t10.org] on behalf of Paul Suhler
[Paul.Suhler at hgst.com]
Sent: Wednesday, June 10, 2015 7:23 PM
To: T10 E-mail Reflector (t10 at t10.org)
Subject: SCSI/ATA Translation of Command Duration Limit (T10/15-093)
I would like to solicit opinions on how to do convert the command duration
limit times expressible in SCSI into the isochronous command completion (ICC)
times expressible in ATA. The problems are:
a) SCSI can express times as low as 1 microsecond, while ATA only goes down
to ten milliseconds.
b) SCSI can express times as large as 32k 1 seconds, while ATA only goes
up to 64 seconds.
c) In some ranges of times, SCSI can express values with a finer granularity
that ATA can.
There are two possible solutions for the SATL:
a) Reject any MODE SELECT command that specifies a value that does not map
precisely to an ATA value; or
b) Round the SCSI value to the nearest ATA value.
Rounding (b) will allow the ATA device to make a best effort at setting a
command duration limit. On the other hand, the value used may be as much as
a factor of 10,000 larger than that specified (1 usec), or as little as
1/500th of that specified (32k-1).
Ill also note that neither ATA nor SCSI has a mechanism to report the actual
range of values supported by a particular device, and neither ACS-4 nor SPC-5
specifies what to do in case of an unsupported value.
Straw poll time. Vote early and vote often!
Paul A. Suhler, PhD
Research Staff Member
paul.suhler at hgst.com
3001 Daimler St.
Santa Ana, CA 92705-5812
More information about the T10