RE: ISCSI: CmdSN in non-leading login

[Bill Studenmund <wrstuden@wasabisystems.com>]

On Mon, 13 May 2002, THALER,PAT (A-Roseville,ex1) wrote:

> John,

I think that was supposed to be me, not John. :-)

> I don't understand your point. An outstanding immediate command
> doesn't affect the progress of ExpCmdSN or MaxCmdSN. In the situation
> you describe, the target would act on the non-immediate commands 1000
> and 1001 when it got them. It would then increase MaxCmdSN as it
> empties those non-immediate commands from its queue.
>
> The login immediate command with CmdSN would be processed when it
> arrives regardless of the current non-immediate command's CmdSN. Any
> immediate command can arrive with a CmdSN lower than ExpCmdSN or
> higher than MaxCmdSN. The use of CmdSN in immediate commands is to
> allow the immediate command to have a relationship to the
> non-immediate commands - e.g. CLEAR TASK SET.

I thought that immediate commands weren't supposed to be processed (or
weren't supposed to be seen to be processed) until their CmdSN came up in
the stream.  From that I also assumed (evidently incorrectly :-) that they
counted against the outstanding command window.

Take care,

Bill