From: Aaron Wood <woody77@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: Mario Ferreira <liouxbsd@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] "BBR" TCP patches submitted to linux kernel
Date: Thu, 29 Sep 2016 21:29:35 -0700 [thread overview]
Message-ID: <CALQXh-Oexda3Hxu0OPrTh+vb_2vwX8CY=X=7=uxMqrNujTN6fg@mail.gmail.com> (raw)
In-Reply-To: <1525bb51-cd92-2656-d48f-bb3a1a659569@taht.net>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
On Thu, Sep 29, 2016 at 8:50 PM, Dave Täht <dave@taht.net> wrote:
>
> > Android is still shipping linux 3.10? How... quaint.
> >
> > 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
>
yet... wouldn't BBR mitigate the local radio fw buffering? The early rtt
probing should (hopefully) see an un-bloated link, and then tune off of
that? So any local buffering would look like any other network path
buffers. True, it doesn't help with downlink data, but it may with the
uplink.
I'm not sure that you can use cake on mobile, not with the sorts of wildly
changing bandwidths that I've been seeing (<5 to >50Mbps within a few
seconds, as one moves through varying lines-of-sight to the tower (say
walking into a building, driving into a tunnel or just past a parking
garage...).
-Aaron
[-- Attachment #2: Type: text/html, Size: 2114 bytes --]
next prev parent reply other threads:[~2016-09-30 4:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 21:04 Dave Taht
2016-09-16 21:11 ` Steinar H. Gunderson
2016-09-16 21:14 ` Eric Dumazet
2016-09-16 22:29 ` Dave Taht
2016-09-29 11:24 ` Mário Sérgio Fujikawa Ferreira
2016-09-29 19:43 ` Dave Täht
2016-09-29 20:35 ` Aaron Wood
2016-09-30 8:12 ` Mikael Abrahamsson
2016-09-30 14:16 ` Aaron Wood
2016-09-29 21:23 ` Steinar H. Gunderson
2016-09-30 1:54 ` Mario Ferreira
2016-09-30 3:50 ` Dave Täht
2016-09-30 4:29 ` Aaron Wood [this message]
2016-09-29 23:26 ` Benjamin Cronce
2016-09-30 1:58 ` Mario Ferreira
2016-10-21 8:47 ` Steinar H. Gunderson
2016-10-21 10:28 ` Eric Dumazet
2016-10-21 10:42 ` Steinar H. Gunderson
2016-10-21 10:47 ` Steinar H. Gunderson
2016-10-21 10:55 ` Eric Dumazet
2016-10-21 10:52 ` Eric Dumazet
2016-10-21 11:03 ` Steinar H. Gunderson
2016-10-21 11:40 ` Eric Dumazet
2016-10-21 11:45 ` Steinar H. Gunderson
2016-10-27 17:04 ` Steinar H. Gunderson
2016-10-27 17:31 ` Eric Dumazet
2016-10-27 17:33 ` Dave Taht
2016-10-27 17:52 ` Eric Dumazet
2016-10-27 17:59 ` Dave Taht
2016-10-27 17:57 ` Yuchung Cheng
2016-10-27 18:14 ` Dave Taht
2016-10-27 21:30 ` [Bloat] [bbr-dev] " Yuchung Cheng
2016-11-01 23:13 ` Yuchung Cheng
2016-11-01 23:49 ` Jonathan Morton
2016-11-02 9:27 ` Mikael Abrahamsson
2016-11-02 17:21 ` Klatsky, Carl
2016-11-02 18:48 ` Dave Täht
2016-11-25 12:51 ` [Bloat] " Bernd Paysan
2016-10-21 10:50 ` Zhen Cao
2016-10-27 19:25 Ingemar Johansson S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-Oexda3Hxu0OPrTh+vb_2vwX8CY=X=7=uxMqrNujTN6fg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=liouxbsd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox