Date: Fri, 17 Feb 2006 11:18:26 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Oliver Brandmueller <ob@e-Gitt.NET> Cc: freebsd-stable@freebsd.org Subject: Re: tcp throughput and net.inet.tcp.inflight.enable Message-ID: <20060217111729.F37321@fledge.watson.org> In-Reply-To: <20060216121604.GE55530@e-Gitt.NET> References: <6.2.3.4.0.20060215221957.076524f8@64.7.153.2> <20060216100359.GA10327@jbell.maths.tcd.ie> <20060216121604.GE55530@e-Gitt.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Feb 2006, Oliver Brandmueller wrote: > On Thu, Feb 16, 2006 at 10:03:59AM +0000, David Malone wrote: >> I think in a situation where your network is fast and large amounts >> of buffering do not imply high latency, then the inflight limiting >> stuff probably isn't useful. >> >> (I have some coworkers who reckon that inflight limiting can do the wrong >> thing in other situations too, but they haven't had a chance to investigate >> their suspicions yet.) > > Maybe it's an idea to make this an per-interface value. On my local GigE NFS > network it might not be useful (well, maybe even lowering the performance), > while on another interface with lots of connects from all over the world > does a good job. > > Dunno, it's probably not so easy to implement this, then. Andre recently committed a change to CVS HEAD to disable inflight limiting when the RTT is very small, as it runs into problems with clock resolution and scaling of predicted bandwidth. I assume this will be merged to RELENG_6 in the near future. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060217111729.F37321>