From: Jonathan Morton <chromatix99@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Michael Richardson <mcr@sandelman.ca>,
Carlo Augusto Grazia <carloaugusto.grazia@unimore.it>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Jamshid Mahdavi <jamshid@whatsapp.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] the future belongs to pacing
Date: Sun, 5 Jul 2020 21:13:39 +0300 [thread overview]
Message-ID: <D7AAE6A6-6339-4D16-9462-D2441A189618@gmail.com> (raw)
In-Reply-To: <20200705110934.55bcfb43@hermes.lan>
> On 5 Jul, 2020, at 9:09 pm, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> I keep wondering how BBR will respond to intermediaries that aggregate packets.
> At higher speeds, won't packet trains happen and would it not get confused
> by this? Or is its measurement interval long enough that it doesn't matter.
Up-thread, there was mention of patches related to wifi. Aggregation is precisely one of the things that would address. I should note that the brief description I gave glossed over a lot of fine details of BBR's implementation, which include careful filtering and conditioning of the data it gathers about the network path.
I'm not altogether a fan of such complexity.
- Jonathan Morton
next prev parent reply other threads:[~2020-07-05 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw5RuBfDA=Yku6+Rm+YEdrUzvZMsoAwVXYduZjBmMVf43Q@mail.gmail.com>
[not found] ` <CALDN43m=2SzkT4vLeqiFxE6PRd+ZKR1hdeMRwtqbTFuAL7nMLA@mail.gmail.com>
2019-12-13 21:25 ` Dave Taht
2020-07-04 17:29 ` Matt Mathis
[not found] ` <mailman.763.1593883755.24343.bloat@lists.bufferbloat.net>
2020-07-04 17:52 ` Daniel Sterling
2020-07-04 18:02 ` Jonathan Morton
2020-07-04 18:29 ` Sebastian Moeller
2020-07-05 6:10 ` Matt Mathis
2020-07-05 12:01 ` Sebastian Moeller
2020-07-05 17:07 ` Matt Mathis
2020-07-05 17:29 ` Sebastian Moeller
2020-07-05 17:43 ` Michael Richardson
2020-07-05 18:09 ` Stephen Hemminger
2020-07-05 18:13 ` Jonathan Morton [this message]
2020-07-05 23:06 ` Matt Mathis
2020-07-06 18:32 ` Roland Bless
2020-07-06 14:08 ` [Bloat] [Make-wifi-fast] " Luca Muscariello
2020-07-06 14:14 ` Daniel Sterling
2020-07-06 17:01 ` Toke Høiland-Jørgensen
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=D7AAE6A6-6339-4D16-9462-D2441A189618@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=carloaugusto.grazia@unimore.it \
--cc=jamshid@whatsapp.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
--cc=stephen@networkplumber.org \
/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