SAS-1.1 overlapped tag handling

Elliott, Robert (Server Storage) elliott at hp.com
Fri Mar 4 15:16:38 PST 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <elliott at hp.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C52110.37F83C81
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

I've posted a proposal 05-107r0 to http://www.t10.org/new.htm
<http://www.t10.org/new.htm>  dealing with (optional) incorrect tag
handling for TASK frames.
=20
In SAS-1, the device server returned a RESPONSE frame containing a
response code of INVALID FRAME if it got a TASK frame with an =
overlapped
tag.  In SAS-1.1, this changed - the device server establishes an I_T
nexus loss (which is a little strange given that a connection for that
I_T is probably still open when this is detected).
=20
Neither of those matches the behavior of incorrect command tags =
(defined
by SAM)(a COMMAND/COMMAND overlap), where the device server returns
CHECK CONDITION/ABORTED COMMAND/OVERLAPPED COMMANDS ATTEMPTED and =
aborts
all tasks for the I_T nexus exhibiting the problem.
=20
This proposal makes the behavior roughly the same for COMMAND/COMMAND,
COMMAND/TASK, TASK/COMMAND, and TASK/TASK conflicts. C/T, T/C, and T/T
combinations return a RESPONSE frame with a response code (rather than =
a
CHECK CONDITION status), and all the cases abort all commands (and task
management functions) for the I_T nexus.
--=20
Rob Elliott, elliott at hp.com=20
Hewlett-Packard Industry Standard Server Storage Advanced Technology=20
https://ecardfile.com/id/RobElliott
<https://ecardfile.com/id/RobElliott> =20

=20

------_=_NextPart_001_01C52110.37F83C81
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

 I've = posted a=20 proposal 05-107r0 to http://www.t10.org/new.htm = dealing with=20 (optional) incorrect tag handling for TASK = frames.
  
 In SAS-1, the device server returned a RESPONSE = frame=20 containing a response code of INVALID FRAME if it got a TASK frame with = an=20 overlapped tag.  In SAS-1.1, this changed - the device server = establishes=20 an I_T nexus loss (which is a little strange given that a connection = for that=20 I_T is probably still open when this is detected).
  
 Neither of those=20 matches the behavior of incorrect command tags (defined by SAM)(a=20 COMMAND/COMMAND overlap), where the device server returns CHECK=20 CONDITION/ABORTED COMMAND/OVERLAPPED COMMANDS ATTEMPTED and aborts = all=20 tasks for the I_T nexus exhibiting the problem.
  
 This = proposal makes=20 the behavior roughly the same for COMMAND/COMMAND, COMMAND/TASK, = TASK/COMMAND,=20 and TASK/TASK conflicts. C/T, T/C, and T/T combinations return a = RESPONSE frame=20 with a response code (rather than a CHECK CONDITION status), and all = the cases=20 abort all commands (and task management functions) for the I_T=20 nexus.
 -- = 
Rob Elliott, = elliott at hp.com=20 
Hewlett-Packard = Industry Standard=20 Server Storage Advanced Technology 
https://ecardfile.com/id/Ro= bElliott=20 

 


------_=_NextPart_001_01C52110.37F83C81--





More information about the T10 mailing list