Ordered Task Tags

Jim McGrath Jim.McGrath at quantum.com
Mon Jan 29 17:59:06 PST 2001


* From the T10 Reflector (t10 at t10.org), posted by:
* Jim McGrath <Jim.McGrath at quantum.com>
*

No - unless you say it is a requirement, it is not a requirement.  That is
why standards often have more of a feel of a legal document than a design
guide.

Specifically, imagine you are given the task of compliance testing and you
had to defend what you were testing.  It is clear that the ORDERED property
is meaningless outside of the context of task sets (i.e. it is not mentioned
except with respect to the task set model), and so you cannot test them in
contexts where task sets do not apply (as in transports).

Jim


-----Original Message-----
From: Santosh Rao [mailto:santoshr at cup.hp.com]
Sent: Friday, January 26, 2001 5:05 PM
To: Gerry.Houlder at seagate.com
Cc: t10 at t10.org
Subject: Re: Ordered Task Tags


Gerry and All,

In the case of a transport protocol that does NOT provide ordered delivery,
does it then become a requirement that the transport order the delivery of
ordered task tag commands ?

IOW, is it the intent of users of ordered task tag commands to obtain
end-to-end ordering, or would they just use CRN for end-to-end ordering ?

Thanks,
Santosh

Gerry.Houlder at seagate.com wrote:

> * From the T10 Reflector (t10 at t10.org), posted by:
> * Gerry.Houlder at seagate.com
> *
>
> The target can only order tasks with respect to the order it receives
them.
> This will match the order sent by the initiator only if in-order delivery
> is guaranteed by the delivery subsystem.
>
> *
> * 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