|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] iSCSI: MaxRecvPDULength simplificationI've
looked over some of the reflector messages regarding MaxRecvPDULength
negotiation (back to Oct 2001). I can't find the discussion of why this
value must be available for negotiation outside of login. It really
complicates SNACK and Task Reassignment if the initiator can change this
value on-the-fly. Would it be too restrictive to propose the
following rules?
1)
MaxRecvPDULength is negotiated only at login before
FFP.
2) For
message-level recovery, a connection must be prepared to accept the
MaxRecvPDULength of the connection it's providing fail over capability
for. It doesn't seem unreasonable to expect fault tolerant configurations
to comply with this. It would simply be stating that RecoveryLevel
2 devices should be somewhat matched in this
capability.
-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Tuesday, March 26, 2002 1:50 AM To: Michael Schoberg Cc: IPS Reflector (E-mail); owner-ips@ece.cmu.edu Subject: Re: iSCSI: SNACK RunLength
Home Last updated: Wed Mar 27 03:18:38 2002 9334 messages in chronological order |