From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 726F73B25E for ; Thu, 29 Sep 2016 23:50:18 -0400 (EDT) Received: from dair-2506.local (c-73-231-152-246.hsd1.ca.comcast.net [73.231.152.246]) (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 E973B2130B; Fri, 30 Sep 2016 03:50:16 +0000 (UTC) To: Mario Ferreira , bloat@lists.bufferbloat.net References: <20160916211120.GA38308@sesse.net> From: =?UTF-8?Q?Dave_T=c3=a4ht?= Message-ID: <1525bb51-cd92-2656-d48f-bb3a1a659569@taht.net> Date: Thu, 29 Sep 2016 20:50:13 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Bloat] "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: Fri, 30 Sep 2016 03:50:18 -0000 On 9/29/16 6:54 PM, Mario Ferreira wrote: > On Thu, Sep 29, 2016, 16:43 Dave Täht > wrote: > > > > On 9/29/16 4:24 AM, Mário Sérgio Fujikawa Ferreira wrote: > > Is there a mailing list I can lurk in to follow on the development? > > > > I'm most interested on a delta to apply to Android 6.x Franco Kernel > > (https://github.com/franciscofranco/angler) > > Android is still shipping linux 3.10? How... quaint. > > > That's for Huawei Nexus 6P. Google's flagship till Pixel XL arrives. > I'll try getting BBR merged to Franco's kernel (officially or maintained > as a fork) and add tc-adv with fq_codel/cake. > > Since this is mobile, I'm pretty sure it will present a whole new host > of "data points". yes! (there have been a few studies of this, btw) The part that we don't really know on the android handsets is how much buffering there really is between qdisc, driver, and firmware, which no doubt varies between models - and within a model on the different wifi and 4G stacks. Odds are - just as we just ripped out on the ath9k/ath10k - so much intermediate buffering exists as to make applying the latency managing qdisc on top of marginal effectiveness. In the case of BBR, well, there is some hope that would regulate TCP on the uplink, but it will have no effect on the down (neither will the qdiscs) - and it requires sch_fq to work properly - which means that you'd have a choice between bbr + sch_fq, or sch_cake/sch_fq_codel. In all cases, acquiring more data and backports would be nice. > > I'm swamped right now but I'll have time by november for both FreeBSD > and Android 6 (7 doesn't have source code released just yet) . I'm no > expert but I'll help as I can. > > > 2. ipfw/dummynet AQM with FQ-Codel > > > (https://lists.freebsd.org/pipermail/freebsd-ipfw/2016-February/006026.html) > > I made some comments on this that I'd like people to look at what is > really going on in bsd + fq_codel at > 100mbit. > > https://github.com/opnsense/core/issues/505 > > > I haven't been involved with the FreeBSD project on recent years but > I'll try to advocate internally. > -- > > Mario S F Ferreira - Brazil - "I guess this is a signature." > feature, n: a documented bug | bug, n: an undocumented feature >