From: Ilpo Järvinen Date: Thu, 9 Aug 2007 11:53:36 +0000 (+0300) Subject: [TCP]: Reduce sacked_out with reno when purging write_queue X-Git-Tag: v2.6.24-rc1~1454^2~818 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1b6d427bb7eb69e6dc4f194a5b0f4a382a16ff82;p=pandora-kernel.git [TCP]: Reduce sacked_out with reno when purging write_queue Previously TCP had a transitional state during which reno counted segments that are already below the current window into sacked_out, which is now prevented. In addition, re-try now the unconditional S+L skb catching. This approach conservatively calls just remove_sack and leaves reset_sack() calls alone. The best solution to the whole problem would be to first calculate the new sacked_out fully (this patch does not move reno_sack_reset calls from original sites and thus does not implement this). However, that would require very invasive change to fastretrans_alert (perhaps even slicing it to two halves). Alternatively, all callers of tcp_packets_in_flight (i.e., users that depend on sacked_out) should be postponed until the new sacked_out has been calculated but it isn't any simpler alternative. Signed-off-by: Ilpo Järvinen Signed-off-by: David S. Miller --- Reading git-diff-tree failed