From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 11E3F3B2A2 for ; Wed, 2 Nov 2016 05:27:10 -0400 (EDT) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 546BCA3; Wed, 2 Nov 2016 10:27:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1478078828; bh=fY/yA4LOe9DorpmvAndNUR7ZvsEvNOo0AZeBIw1kjvI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=mWjxrt/orSasQZsGkYkvIkGavkt0riN4DuBgZkm9QzgB5eKLlWPVNLzhn+KLlrlm9 TxaHNC5Beg71jNhIpMEmAQWqUczr5dl7KSaW04ZW+aCwqXKK96sTGkIwTHT/lurBNz 91jnKRb0gLqhS0x4pVnQOGnw6GRt1LSYOAFM/mNc= Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4F8B2A2; Wed, 2 Nov 2016 10:27:08 +0100 (CET) Date: Wed, 2 Nov 2016 10:27:08 +0100 (CET) From: Mikael Abrahamsson To: Yuchung Cheng cc: BBR Development , bloat In-Reply-To: Message-ID: References: <20161021084726.GA1913@sesse.net> <20161027170447.GA28383@sesse.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) Organization: People's Front Against WWW MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1898461149-1478078828=:14320" 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 09:27:10 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---137064504-1898461149-1478078828=:14320 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT 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. -- Mikael Abrahamsson email: swmike@swm.pp.se ---137064504-1898461149-1478078828=:14320--