Re: [RFC PATCHv5 1/5] [TCP]: Add highest_sack seqno, points to globally highest SACK

2007-03-26 Thread Ilpo Järvinen
On Sun, 25 Mar 2007, David Miller wrote: From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Mon, 26 Mar 2007 00:55:57 +0300 (EEST) On Sat, 24 Mar 2007, David Miller wrote: From: Ilpo_Järvinen [EMAIL PROTECTED] It is guaranteed to be valid only when !tp-sacked_out. In most cases

Re: [RFC PATCHv5 1/5] [TCP]: Add highest_sack seqno, points to globally highest SACK

2007-03-25 Thread Ilpo Järvinen
On Sat, 24 Mar 2007, David Miller wrote: From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Fri, 16 Mar 2007 20:41:02 +0200 It is guaranteed to be valid only when !tp-sacked_out. In most cases this seqno is available in the last ACK but there is no guarantee for that. The new fast recovery

Re: [RFC PATCHv5 1/5] [TCP]: Add highest_sack seqno, points to globally highest SACK

2007-03-25 Thread David Miller
From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Mon, 26 Mar 2007 00:55:57 +0300 (EEST) On Sat, 24 Mar 2007, David Miller wrote: From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Fri, 16 Mar 2007 20:41:02 +0200 It is guaranteed to be valid only when !tp-sacked_out. In most cases this seqno

Re: [RFC PATCHv5 1/5] [TCP]: Add highest_sack seqno, points to globally highest SACK

2007-03-24 Thread David Miller
From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Fri, 16 Mar 2007 20:41:02 +0200 It is guaranteed to be valid only when !tp-sacked_out. In most cases this seqno is available in the last ACK but there is no guarantee for that. The new fast recovery loss marking algorithm needs this as entry point.

[RFC PATCHv5 1/5] [TCP]: Add highest_sack seqno, points to globally highest SACK

2007-03-16 Thread Ilpo Järvinen
It is guaranteed to be valid only when !tp-sacked_out. In most cases this seqno is available in the last ACK but there is no guarantee for that. The new fast recovery loss marking algorithm needs this as entry point. Signed-off-by: Ilpo Järvinen [EMAIL PROTECTED] --- include/linux/tcp.h |2