Re: iSCSI : Command Ordering Proposal.

[Santosh Rao <santoshr@cup.hp.com>]

Charles Binford wrote:

> Seems to me like adding a new CRN field for command ordering (if the
> application so chooses) and re-defining the CmdRN field to only provide the
> flow control satisfies the requirements without overloading the
> functionality of a single field.
>

This is exactly my point. Strict ordering should only be enforced when
driven by an application. (either through the use of Ordered Task Tags for
task set ordering or the use of CRN for end-to-end ordering).

The use of CmdSN to order all commands seems an over-kill when those
applications that did need ordering would use the Ordered Task Tag or
CRN, based on their need.

Strict ordering is only required for the aborts that follow their commands.

Also, it would be helpful to re-name the new 1-byte CmdRN in the
new iSCSI PDU to CRN to avoid confusion with the old semantics of
CmdRN. (which is now the CmdSN !!)

Regards,
Santosh
begin:vcard 
n:Rao;Santosh 
tel;work:408-447-3751
x-mozilla-html:FALSE
org:Hewlett Packard, Cupertino.;SISL
adr:;;19420, Homestead Road, M\S 43LN,	;Cupertino.;CA.;95014.;USA.
version:2.1
email;internet:santoshr@cup.hp.com
title:Software Design Engineer
x-mozilla-cpt:;21088
fn:Santosh Rao
end:vcard