From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 566183B2A3 for ; Wed, 2 Nov 2016 14:48:10 -0400 (EDT) Received: from dair-2506.local (67-0-210-21.albq.qwest.net [67.0.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 017B721329 for ; Wed, 2 Nov 2016 18:48:08 +0000 (UTC) To: bloat@lists.bufferbloat.net References: <20161021084726.GA1913@sesse.net> <20161027170447.GA28383@sesse.net> <6ca4aea40ca34ec4b04648f23416da40@PACDCEX43.cable.comcast.com> From: =?UTF-8?Q?Dave_T=c3=a4ht?= Message-ID: <237908b5-15d1-b5ae-8e2d-0927c14a151e@taht.net> Date: Wed, 2 Nov 2016 12:48:07 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <6ca4aea40ca34ec4b04648f23416da40@PACDCEX43.cable.comcast.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Bloat] [bbr-dev] Re: "BBR" TCP patches submitted to linux kernel X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 18:48:10 -0000 On 11/2/16 11:21 AM, Klatsky, Carl wrote: >> On Tue, 1 Nov 2016, Yuchung Cheng wrote: >> >>> We are curious why you choose the single-queued AQM. Is it just for >>> the sake of testing? >> >> Non-flow aware AQM is the most commonly deployed "queue >> management" on the Internet today. Most of them are just stupid FIFOs >> with taildrop, and the buffer size can be anywhere from super small to huge >> depending on equipment used and how it's configured. >> >> Any proposed TCP congestion avoidance algorithm to be deployed on the >> wider Internet has to some degree be able to handle this deployment >> scenario without killing everything else it's sharing capacity with. >> >> Dave Tähts testing case where BBR just kills Cubic makes me very concerned. > > If I am understanding BBR correctly, that is working in the sender to receiver direction. In Dave's test running TCP BBR & TCP CUBIC with a single queue AQM, where CUBIC gets crushed. The scenario as I constructed it was emulating a sender on "home" side of the link, using BBR and cubic through an emulated cablemodem running pie. Silly question, but the single queue AQM was also operating in the in sender to receiver direction for this test, yes? > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >