Date: Tue, 12 Jul 2005 10:48:24 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Danny Braniss <danny@cs.huji.ac.il> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Luigi Rizzo <rizzo@icir.org> Subject: Re: tcp troughput weirdness Message-ID: <200507121048.ab72454@salmon.maths.tcd.ie> In-Reply-To: Your message of "Tue, 12 Jul 2005 12:21:23 %2B0300." <E1DsGx9-0008Xc-GW@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
> did the trick! now can someone remind me what inflight does? and could > someone explain why increasing sendspace alone did not do the trick? > (i had it at 64k, which got things better, but not sufficient). TCP inflight limiting is supposed to guess the bandwidth-delay product for a TCP connection and stop the window expanding much above this. It's a pretty neat idea for DSL links that often have huge buffers at the far end, where inflight limiting can prevent delays to interactive traffic. However, some of the guys I know that work on TCP dynamics reckon that they can they can come up with situations where inflight limiting will break. Unfortunately, I haven't had time to talk this through with them. I guess you may have found one of those situations ;-) David.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507121048.ab72454>