|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI: ImmediateData & InitialR2TAyman, iSCSI connections are not separate entities. Commands are sent over a session and connection should not be visible over a certain level. Using Immediate data belongs to a very high level layer (where the endpoint facilities are handled). Connections should have nothing to say about it. Julo
The text doesn't say these are connection specific, so they must be session specific. Connection 1 logs in and doesn't send the ImmediateData key because it wants to use the default "yes". If connection 2 sends ImmediateData=no and the target agrees to that, how is this going to affect connection 1 which thinks it can send immediate data, and may actually have data in flight to the target. I think these two keys should have the same use restrictions as DataPDULength, FirstBurstSize, and MaxBurstSize, all have Use:LO. -Ayman > -----Original Message----- > From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of > Julian Satran > Sent: Friday, October 05, 2001 4:24 AM > To: ips@ece.cmu.edu > Subject: Re: iSCSI: ImmediateData & InitialR2T > > > > why ? Julo > > > > > "Ayman Ghanem" > > <aghanem@cisco To: > <ips@ece.cmu.edu> > .com> cc: > > Sent by: Subject: iSCSI: > ImmediateData & InitialR2T > owner-ips@ece. > > cmu.edu > > > > > > 04-10-01 17:42 > > Please respond > > to "Ayman > > Ghanem" > > > > > > > > > Julian, > > The use of these two keys is currently set to "Use: ALL". I think they > should be allowed only on the leading connection, so a second connection > can > not change them on the first. > > -Ayman > > > > > >
Home Last updated: Sat Oct 06 10:17:45 2001 7090 messages in chronological order |