increase-the-max_burst-threshold-from-3-to-tp-reordering.patch added to queue-2.6.22.23-op1
Subsystems (2)
Your patch added to queue-2.6.22.23-op1.
If anyone has any objections, please let us know.
http://repo.or.cz/w/linux-2.6.22.y-op-patches.gitgit://repo.or.cz/linux-2.6.22.y-op-patches.git
---
Quoted 1 line
From
3c0390e1a6d8a5d0cdae57959f0be37a236b474dMon Sep 17 00:00:00 2001
From: John Heffner <jheffner@napa.(none)>
Date: Fri, 25 Apr 2008 01:43:57 -0700
Subject: [PATCH] [TCP]: Increase the max_burst threshold from 3 to tp->reordering.
From: John Heffner <jheffner@napa.(none)>
[ Upstream commit: dd9e0dda66ba38a2ddd1405ac279894260dc5c36 ]
This change is necessary to allow cwnd to grow during persistent reordering. Cwnd moderation is applied when in the disorder state and an ack that fills the hole comes in. If the hole was greater than 3 packets, but less than tp->reordering, cwnd will shrink when it should not have.
--- include/net/tcp.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
include/net/tcp.h +5 -2
@@ -775,11 +775,14 @@ extern void tcp_enter_cwr(struct sock *sextern __u32 tcp_init_cwnd (struct tcp_sock *tp,struct dst_entry *dst);/* Slow start with delack produces 3 packets of burst, so that -* it is safe "de facto". +* it is safe "de facto". This will be the default - same as +* the default reordering threshold - but if reordering increases, +* we must be able to allow cwnd to burst at least this much in order +* to not pull it back when holes are filled. */ static __inline____u32 tcp_max_burst (const struct tcp_sock *tp) { -return 3 ; +return tp->reordering; }/* RFC2861 Check whether we are limited by application or congestion
window