From: Matthias Tafelmeier <matthias.tafelmeier@gmx.net>
To: bloat@lists.bufferbloat.net, "Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Tue, 12 Jun 2018 07:09:01 +0200 [thread overview]
Message-ID: <7adae673-d701-6fe0-1d47-524320d38583@gmx.net> (raw)
In-Reply-To: <87in6ohm30.fsf@toke.dk>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 696 bytes --]
On 06/12/2018 02:42 AM, Toke Høiland-Jørgensen wrote:
>> https://ripe76.ripe.net/presentations/10-2018-05-15-bbr.pdf
> "More research needed". Naturally ;)
>
> (But yeah, good points overall)
Interesting. Potentially, all affectuated. After having applied the BBR
2.0, we might are back to Cubic? :D
Moreover, if it tends to be unstable on larger scale - what is Google
doing then? Thought they've got a more or less homogeneous BBR driven
TCP flow ecosystem - at least internally!? Was all propaganda? When
speculating, might working for them since of centrally handled flow
steering approaches - "imposing inter-flow fairness".
--
Besten Gruß
Matthias Tafelmeier
[-- Attachment #1.1.1.2: Type: text/html, Size: 1436 bytes --]
[-- Attachment #1.1.2: 0xE0164F5B8ADF343B.asc --]
[-- Type: application/pgp-keys, Size: 5250 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next prev parent reply other threads:[~2018-06-12 5:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 21:27 Dave Taht
2018-06-12 0:42 ` Toke Høiland-Jørgensen
2018-06-12 5:09 ` Matthias Tafelmeier [this message]
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
2018-06-12 6:55 Dave Taht
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
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=7adae673-d701-6fe0-1d47-524320d38583@gmx.net \
--to=matthias.tafelmeier@gmx.net \
--cc=bloat@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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