SRP Task Tags
Elliott, Robert (Server Storage)
Elliott at hp.com
Sat Jul 6 23:39:39 PDT 2002
* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
> -----Original Message-----
> From: John Middleton [mailto:jmiddleton at banderacom.com]
> Sent: Friday, July 05, 2002 2:28 PM
> To: t10 at t10.org
> Subject: SRP Task Tags
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "John Middleton" <jmiddleton at banderacom.com>
> I'm reviewing task management functions in SRP. I've
> concluded that the task management requirements are
> relatively light as compared to the capabilities laid out in
> SAM-2. It appears to me that if the LINK bit in a CDB is
> set, the fact that each SRP request has a unique task tag
> would essentially disallow linked commands and the
> construction of task sets. Therefore, most of the task set
> capabilities in SAM-2 are not applicable to SRP implementations.
An application client requesting a task containing linked commands can only have one command active at a time (see SAM-2 5.1), so there's no confusion about which tag to use to abort the task.
A "task set" is all the tasks outstanding at a time, not the set of linked commands that may comprise a task. Each task has one only command outstanding at a time; a task set could include a mix of unlinked tasks and linked tasks.
SRP supports linked commands the same as all the other SCSI transport protocols.
> John Middleton
> jmiddleton at banderacom.com
> * 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