SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    Re: iSCSI: Use of the A bit



    Dear all,
    
    The text for the A bit part (9.7.2) reads now:
    
       A (Acknowledge) bit
    
    
           For sessions with ErrorRecoveryLevel 1 or higher, the target sets
           this bit to 1 to indicate that it requests a positive
           acknowledgement from the initiator for the data received.  The
           target should use the A bit moderately; it MAY set the A bit to 1
           only once every MaxBurstSize bytes or on the last Data-In PDU that
           concludes the entire requested read data transfer for the task from
           the target's perspective, and MUST NOT do so more frequently than
           this.
    
           On receiving a Data-In PDU with the A bit set to 1, the initiator
           MUST issue a SNACK of type DataACK.  If the initiator has detected
           holes in the input sequence, it MUST postpone issuing the SNACK of
           type DataACK until the holes are filled. An initiator MUST ONLY
           acknowledge the status for command that produced Data-In PDUs after
           acknowledging the Data-In PDUs if Data-In PDU acknowledgment is
           requested by the target. A status acknowledgement for a command that
           generated Data-In PDUs is considered by the target as an implicit
           acknowledgement of the Data-In PDUs if such an acknowledgement was
           requested by the target.
    
    The ITT mandating text in 9,16.1 will read:
    
           For Status SNACK and DataACK, the Initiator Task Tag is reserved. In
           all other cases, the Initiator Task Tag field MUST be set to the
           Ini-tiator Task Tag of the referenced command.
    
    
           Julo
    
    


Home

Last updated: Mon Mar 18 07:18:24 2002
9172 messages in chronological order