General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Bloat] TCP BBR paper is now generally available
Date: Fri, 2 Dec 2016 11:15:41 -0800	[thread overview]
Message-ID: <CALQXh-Pr+RNux5w6phqaw4kKifbB2j38JWBjCVBEog1GCYBafw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7DfMY4qHnbxYDUN8hfpgY_aNxa1LcyPKd6pa93qXe2Kw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

This is really fascinating reading.

The following made me stop for a second, though:

"The bucket is typically full at connection startup so BBR learns the
underlying network's BtlBw, but once the bucket empties, all packets sent
faster than the (much lower than BtlBw) bucket fill rate are dropped. BBR
eventually learns this new delivery rate, but the ProbeBW gain cycle
results in continuous moderate losses. To minimize the upstream bandwidth
waste and application latency increase from these losses, we added policer
detection and an explicit policer model to BBR."

So, how is this likely to be playing with our qos_scripts and with cake?

Given we have people from both Google and qos_scripts/cake development
here, do we need to compare some notes on how these interact?  Are there
settings in the HTB setup used by qos_scripts that will make it play more
nicely with BBR (smaller quantums, smaller burst sizes, etc)?

-Aaron


On Fri, Dec 2, 2016 at 7:52 AM, Dave Taht <dave.taht@gmail.com> wrote:

> http://queue.acm.org/detail.cfm?id=3022184
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2168 bytes --]

  reply	other threads:[~2016-12-02 19:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 15:52 Dave Taht
2016-12-02 19:15 ` Aaron Wood [this message]
2016-12-02 20:32   ` Jonathan Morton
2016-12-02 22:22     ` Neal Cardwell
2016-12-02 22:40       ` Steinar H. Gunderson
2016-12-02 23:31         ` Eric Dumazet
2016-12-03 13:03           ` Neal Cardwell
2016-12-03 19:13             ` Steinar H. Gunderson
2016-12-03 20:20               ` Eric Dumazet
2016-12-03 20:26                 ` Jonathan Morton
2016-12-03 21:07                   ` Eric Dumazet
2016-12-03 21:34                     ` Steinar H. Gunderson
2016-12-03 21:50                       ` Eric Dumazet
2016-12-03 22:13                         ` Steinar H. Gunderson
2016-12-03 22:55                           ` Eric Dumazet
2016-12-03 23:02                             ` Eric Dumazet
2016-12-03 23:09                               ` Eric Dumazet
2016-12-03 23:03                             ` Steinar H. Gunderson
2016-12-03 23:15                               ` Eric Dumazet
2016-12-03 23:24                                 ` Eric Dumazet
2016-12-04  3:18                                   ` Neal Cardwell
2016-12-04  8:44                                   ` Steinar H. Gunderson
2016-12-04 17:13                                     ` Eric Dumazet
2016-12-04 17:38                                       ` Steinar H. Gunderson
2016-12-06 17:20                                   ` Steinar H. Gunderson
2016-12-06 21:31                                     ` Neal Cardwell
2016-12-03 21:38                     ` Jonathan Morton
2016-12-03 21:33                 ` Steinar H. Gunderson
2016-12-07 16:28               ` Alan Jenkins
2016-12-07 16:47                 ` Steinar H. Gunderson
2016-12-07 17:03                   ` Alan Jenkins
2016-12-08  8:24 ` Mikael Abrahamsson
2016-12-08 13:22   ` Dave Täht
2016-12-08 14:01     ` Mikael Abrahamsson
2016-12-08 21:29       ` Neal Cardwell
2016-12-08 22:31         ` Yuchung Cheng
2016-12-09 14:52           ` Klatsky, Carl

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-Pr+RNux5w6phqaw4kKifbB2j38JWBjCVBEog1GCYBafw@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@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