4/17 - SPL-2 letter ballot comment resolution meeting

Penokie, George George.Penokie at lsi.com
Mon Apr 16 13:48:20 PDT 2012


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1204170_f.htm">HTML-formatted message</a>

This is a reminder that there will be an SPL-2 letter ballot comment
resolution meeting tomorrow (4/17) from 3 PM to 5 PM central time. The main
topic of the meeting will be Tx Training proposals. But first we will discuss
3 new comments from Rob Elliott. Those comments follow. If you have any
interest in resisting these comments you should be on the call because, at
this time,  I have no objection to them:
There are two comments on Table 191 - Send Command Complete transport
protocol service arguments about the  Service Response argument. Those
comments are:
This is the operation used by the device server uses to tell the SAS target
port what to put in the RESPONSE frame.  It needs to pass along the full
"SERVICE DELIVERY OR TARGET FAILURE - reason" to decide which RESPONSE CODE
value to use.
Change this:
Specifies the DATAPRES field and STATUS field in the RESPONSE frame:
a) COMMAND COMPLETE: The DATAPRES field is set to NO_DATA or SENSE_DATA; or
b) SERVICE DELIVERY OR TARGET FAILURE: The DATAPRES field is set to
RESPONSE_DATA and the RESPONSE CODE field is set to INVALID FRAME or
OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED.
To:
Specifies in the RESPONSE frame:
a) COMMAND COMPLETE: The DATAPRES field is set to NO_DATA or SENSE_DATA;
b) SERVICE DELIVERY OR TARGET FAILURE - Invalid Frame: The DATAPRES field is
set to RESPONSE_DATA and the RESPONSE CODE field is set to INVALID FRAME; or
c) SERVICE DELIVERY OR TARGET FAILURE - Overlapped Initiator Port Transfer
Tag Attempted: The DATAPRES field is set to RESPONSE_DATA and the RESPONSE
CODE field is set to OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED.
And
For the Service Response I don't see any place where the device server
reports INVALID FRAME.	The SAS target port state machines send that on their
own (e.g., in 8.2.6.3.3.2).   So, that item is completely unnecessary and
should be deleted.
There is one comment on Table 201 - Task Management Function Executed
transport protocol service arguments about the Service Response argument.
That comment is:
I don't see any place that the task manager sends INVALID FRAME.  9.2.4 does
have it send OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED, and TASK
MANAGEMENT FUNCTION FAILED would only come from the task manager too (that's
covered in SAM-5, not SPL-2).
So this:
SERVICE DELIVERY OR TARGET FAILURE: The RESPONSE frame DATAPRES field is set
to RESPONSE_DATA and the RESPONSE CODE field is set to:
A) INVALID FRAME;
B) TASK MANAGEMENT FUNCTION FAILED; or
C) OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED.
Should be:
e) TASK MANAGEMENT FUNCTION FAILED: The DATAPRES field is set to
RESPONSE_DATA and the RESPONSE CODE field is set to TASK MANAGEMENT FUNCTION
FAILED; and
f) SERVICE DELIVERY OR TARGET FAILURE - Overlapped Initiator Port Transfer
Tag Attempted: The DATAPRES field is set to RESPONSE_DATA and the RESPONSE
CODE field is set to OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED.
Bye for now,
George Penokie
LSI Corporation
3033 41 St NW
Rochester , MN 55901
507-328-9017
george.penokie at lsi.com



More information about the T10 mailing list