From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: bloat <bloat@lists.bufferbloat.net>, Geoff Huston <gih@apnic.net>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Mon, 11 Jun 2018 23:55:10 -0700 [thread overview]
Message-ID: <CAA93jw60AqzE5dMzmz76Z2HcfN_MrEde86r+0OUjupv5V9_kyw@mail.gmail.com> (raw)
On Mon, Jun 11, 2018 at 10:58 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
>
>
>> On 11 Jun 2018, at 22:27, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> https://ripe76.ripe.net/presentations/10-2018-05-15-bbr.pdf
>
> Fascinating!
>
> " • BBR changes all those assumptions, and could potentially push many networks into sustained instability
>
> • – We cannot use the conventional network control mechanisms to regulate BBR flows
>
> • Selective packet drop just won’t create back pressure on the flow”
>
> And I keep on seeing questions on whether BBR understands ECN - if not…. well I think we see the results.
I think geoff goofed in his testing of BBR, starting all flows at the
same time, thus syncing up their probing periods. Real traffic is not
correlated this way.
(I made the same mistake on my initial bbr testing)
I do agree that bbr treats aqm drops as "noise", not backpressure. And
bbr scares me.
I look forward very much to bbr one day soon doing some sort of sane,
conservative, response to ecn marks.
PS having fq on the link makes cubic and bbr cohabitate just fine.
fq_codel vs bbr behavior was reasonable, though bbr lost a lot more
packets before finding a decent state.
> Cheers,
>
> Kevin D-B
>
> 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2018-06-12 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 6:55 Dave Taht [this message]
2018-06-12 7:49 ` Geoff Huston
2018-06-12 11:25 ` Dave Taht
2018-06-12 15:58 ` Bless, Roland (TM)
2018-06-12 23:02 ` Geoff Huston
2018-06-13 7:56 ` Bless, Roland (TM)
2018-06-12 22:28 ` Greg White
2018-06-12 23:04 ` Anna Brunstrom
2018-06-12 14:29 ` Jim Gettys
-- strict thread matches above, loose matches on Subject: below --
2018-06-11 21:27 Dave Taht
2018-06-12 0:42 ` Toke Høiland-Jørgensen
2018-06-12 5:09 ` Matthias Tafelmeier
2018-06-12 7:36 ` Bless, Roland (TM)
2018-06-12 11:40 ` Dave Taht
2018-06-12 12:00 ` Dave Taht
2018-06-12 17:06 ` Matthias Tafelmeier
2018-06-12 5:58 ` Kevin Darbyshire-Bryant
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=CAA93jw60AqzE5dMzmz76Z2HcfN_MrEde86r+0OUjupv5V9_kyw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=gih@apnic.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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