From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3425.houston.hp.com (g4t3425.houston.hp.com [15.201.208.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.hp.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 0A17621F3B0 for ; Thu, 25 Sep 2014 09:09:38 -0700 (PDT) Received: from g9t2301.houston.hp.com (g9t2301.houston.hp.com [16.216.185.78]) by g4t3425.houston.hp.com (Postfix) with ESMTP id 5E151F9; Thu, 25 Sep 2014 16:09:37 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g9t2301.houston.hp.com (Postfix) with ESMTP id 6B47884; Thu, 25 Sep 2014 16:09:35 +0000 (UTC) Message-ID: <54243E3E.6080806@hp.com> Date: Thu, 25 Sep 2014 09:09:34 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Mikael Abrahamsson , David Lang References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bloat Subject: Re: [Bloat] I feel an urge to update this X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 16:10:07 -0000 >> using fq_codel on every bottleneck link will make TCP work pretty well >> across that entire range of connectivity > > Well, that'll fix one thing, but for instance the IW4 and IW10 debate. > I'm sure IW10 works *great* on a 100/100 megabit/s connection when the > server is 10GE connected, but it's less than optimal for a 0.1 megabit/s > connection. > > So why can't the client hint the server that, hmm, I seem to be on a > fairly slow connection here, don't send me too much at once? Or it can > hint that hey, it seems most times I get pretty large TCP window sizes, > so it's ok to start with IW10? Well, there has been such a thing present in TCP from "The Beginning" though not named as such. Such a client could always advertise a smaller (initial) receive window... One which would allow only IW3 or whatever value was appropriate. rick jones