SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    iSCSI: FirstBurstSize and unsolicited data


    • To: <ips@ece.cmu.edu>
    • Subject: iSCSI: FirstBurstSize and unsolicited data
    • From: "Nandakumar Ramamurthy" <nramamur@npd.hcltech.com>
    • Date: Fri, 14 Jun 2002 16:45:56 +0530
    • Content-Transfer-Encoding: 7bit
    • Content-Type: text/plain;charset="iso-8859-1"
    • Organization: HCL Technologies Ltd.
    • Sender: owner-ips@ece.cmu.edu

    Hi All,
    
    Consider the case where InitialR2T=yes and ImmediateData=yes.
    All other values are the defaults.
    
    The expected data transfer length for a SCSI write
    operation is a value exceeding FirstBurstSize (64KB).
    
    In the above case, the initiator will send immediate
    unsolicited data (MaxRecvPDULength=8192 bytes).
    After that it has to wait for an R2T from the target.
    
    In this scenario, FirstBurstSize of data will not be sent
    to the target as unsolicited data-out's cannot be sent here.
    
    My understanding is that the remaining data can be
    sent only through solicited Data-out PDUs,
    and this is the expected way according to the draft.
    
    What does the following statement(in Section 9.4.6.2 Sense Data) mean in
    this context ?
    
    <quote>
    
    The target reports the "Not enough unsolicited data" condition only
    if it does not support output (write) operations in which the total
    
    data length is greater than FirstBurstSize, but the initiator sent
    
    less than FirstBurstSize amount of unsolicited data, and out-of-order
    
    R2Ts cannot be used.
    
    </quote>
    
    If this is specific to the SCSI layer at the target,
    what is the dependency on FirstBurstSize?
    
    Please clarify.
    
    Thanks,
    Nandakumar
    Member Technical Staff
    HCL Technologies, Chennai, INDIA.
    http://san.hcltech.com
    
    
    


Home

Last updated: Fri Jun 14 14:18:43 2002
10820 messages in chronological order