SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    RE: iSCSI: changing MaxPDUDataLength



    Thanks,
    
    As a target, I won't be able to let it change until all of the outstanding
    commands are finished (running with ErrorRecoveryLevel>=1). This is because
    I must use the PDU size to compute the offset from a SNACK's
    BegRun/RunLength.
    
    So, I plan to not give the text response for a MaxPDURecvDataLength in FFP
    until I get back an ExpStatSN == next StatSN.
    
    This will cause a delay of unknown time before the PDU size can actually
    change ... do you see any problem with this?
    
    Eddy
    
    -----Original Message-----
    From: pat_thaler@agilent.com [mailto:pat_thaler@agilent.com]
    Sent: Friday, June 07, 2002 1:13 PM
    To: eddy_quicksall@ivivity.com; ips@ece.cmu.edu
    Subject: RE: iSCSI: changing MaxPDUDataLength
    
    
    Eddy,
    
    If one uses a message sync and steering that relys on the transport segments
    carrying a full PDU, e.g. TCP ULP Framing Protocol (TUF), then if the path
    MTU changes one would want to change the PDU data length to fit the new path
    MTU.
    
    Pat
    
    -----Original Message-----
    From: Eddy Quicksall [mailto:eddy_quicksall@ivivity.com]
    Sent: Wednesday, June 05, 2002 12:24 PM
    To: ips@ece.cmu.edu
    Subject: iSCSI: changing MaxPDUDataLength
    
    
    Does anybody know a case where it is necessary to support a new PDU data
    length during full feature phase?
     
    Eddy
    mailto: Eddy_Quicksall@iVivity.com
     
    


Home

Last updated: Sat Jun 08 23:18:42 2002
10612 messages in chronological order