|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI: SNACK R2T/DataI am very much in favour of having a positive ACK mechanism to control buffer resources at the target. If there is a very large transfer (e.g. 1 Mb) then the sender can release buffer space once it knows that the receiver has received the data. It is worth pointing out that this mechanism is for buffer control and is not for flow control which, as we all know, is handled by TCP. Cheers Matthew Burbridge Senior Development Engineer NIS-Bristol Hewlett Packard Telnet: 312 7010 E-mail: matthewb@bri.hp.com -----Original Message----- From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Wednesday, September 19, 2001 6:28 AM To: ips@ece.cmu.edu Subject: Re: iSCSI: SNACK R2T/Data There is no ACK mechanism. The group wisdom was that there is no need for one. Incoming data and R2Ts are not acked (a mechanism that did that existed and was based on NOP-Out). Julo Michael Schoberg <michael_schoberg@cnt.com> on 18-09-2001 19:09:51 Please respond to Michael Schoberg <michael_schoberg@cnt.com> To: "'ips@ece.cmu.edu'" <ips@ece.cmu.edu>, Julian Satran/Haifa/IBM@IBMIL cc: Subject: iSCSI: SNACK R2T/Data Old subject, but I couldn't find any discussion on this: When does the target know it no longer needs to hold R2T & Data PDUs? StatSN responses are acknowledged through the ExpStatSN field received in future I->T requests. What's the acknowledgement method for R2T & Data PDUs? Is it tied to the original request and acknowledged through the ExpStatSN acknowledgment of the request's response? Thanks.
Home Last updated: Thu Sep 20 01:17:11 2001 6619 messages in chronological order |