Message-ID: <1BEBA5E8600DD4119A50009027AF54A0132E0486@axcs04.cos.agilent.com>
From: pat_thaler@agilent.com
To: julian@cs.haifa.ac.il, Black_David@emc.com
Cc: dcuddihy@attotech.com, ips@ece.cmu.edu
Subject: RE: StatSN and overlapped commands
Date: Tue, 5 Aug 2003 12:54:05 -0600 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Julian,

I agree that the initiator is misbehaving, but I don't agree that the target should detect that misbehavior. The target SCSI layer thinks the command was done when it generated the status. As David said, the target keeps the status around so that it can resend it if requested by Status SNACK. It doesn't need to keep track of the tag anymore at that point.

If the target had to generate an error when a command came with for a tag before the status for a prior command with the same tag was acknowledged, then it would have to clear the memory of tags when status acks came in which is less efficient than doing it when posting the status.

Pat

-----Original Message-----
From: Julian Satran [mailto:julian@cs.haifa.ac.il]
Sent: Tuesday, August 05, 2003 10:56 AM
<snip>
> 
> 
> No, iSCSI at the target is retaining the SCSI status of the completed
> command for retransmission.  SCSI believes the command to be completed,
> and any retransmission request (e.g., Status SNACK) is not visible to
> SCSI at the target.  In this case "command recovery" does not execute
> any commands at the target; it just causes retransmission of the saved
> status.
> 
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Senior Technologist
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> black_david@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
> 
My only caveat to this would be that an initiator that reuses the 
Initiator Task Tag but does not acknowledge the reception of the status 
by an ExpSataSN is definitely misbehaving.

The target should not consider it as an implicit ack (as intermetiate 
status PDUs may have been lost - it should reject the command that 
reuses the Initiator Task Tag.

That is not necesarily related to the way an initiator maps SCSI tags to 
iSCSI tags - it is specific to iSCSI expectations about tag reuse.

You correctly stated that an iSCSI tag should not be reused before it's 
status is acknowledged but violating this rule is an iSCSI protocol 
error and not a SCSI error (overlapped command).

Julo