From: Jonathan Morton <chromatix99@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, "aqm@ietf.org" <aqm@ietf.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] TCP BBR paper is now generally available
Date: Fri, 2 Dec 2016 22:32:14 +0200 [thread overview]
Message-ID: <56F6A3AB-3A47-4178-BEFF-04E3DC23B039@gmail.com> (raw)
In-Reply-To: <CALQXh-Pr+RNux5w6phqaw4kKifbB2j38JWBjCVBEog1GCYBafw@mail.gmail.com>
> On 2 Dec, 2016, at 21:15, Aaron Wood <woody77@gmail.com> wrote:
>
> So, how is this likely to be playing with our qos_scripts and with cake?
Cake’s deficit-mode shaper behaves fairly closely like an ideal constant-throughput link, which is what BBR is supposedly designed for. I haven’t read that far in the paper yet, but it shouldn’t trigger any “bucket detection” algorithms, because it doesn’t have a “bucket”. It is capable of bursting, but only to the minimum extent required to reconcile required throughput with timer resolution and scheduling latency; I’ve tested it with millisecond timers.
The older schemes involving HTB and HFSC *do* have token-bucket behaviour, with an explicitly configured burst size (this excess traffic will collect in downstream buffers). However, these are shapers, not policers, so they will start delaying packets (leaving them in child qdiscs) when the bucket is empty, not simply dropping them.
The interaction with AQM-related marking and dropping will be interesting to read, though. It’s not a-priori obvious how much a shaper-AQM combination looks like a policer.
- Jonathan Morton
next prev parent reply other threads:[~2016-12-02 20:32 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
2016-12-02 20:32 ` Jonathan Morton [this message]
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=56F6A3AB-3A47-4178-BEFF-04E3DC23B039@gmail.com \
--to=chromatix99@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=woody77@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