From: Matt Mathis <mattmathis@google.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Carlo Augusto Grazia <carloaugusto.grazia@unimore.it>,
bloat <bloat@lists.bufferbloat.net>,
Jamshid Mahdavi <jamshid@whatsapp.com>
Subject: Re: [Bloat] the future belongs to pacing
Date: Sun, 5 Jul 2020 16:06:42 -0700 [thread overview]
Message-ID: <CAH56bmB+LFpDFmDDAcnJ1KA8=T62BiZ9jSKROd6EFcmRTO7Vwg@mail.gmail.com> (raw)
In-Reply-To: <D7AAE6A6-6339-4D16-9462-D2441A189618@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
What the complexity buys you is that BBRs metrics max_BW, min_RTT, and the
ACK aggregation/batching metrics are actual parameters of the network, and
observable with passive instrumentation of the packet streams. Traditional
CC is a collection of heuristics to estimate cwnd, which has a clear
interpretation in terms of action (when to send), but the optimal cwnd
can't easily be observed from the packet stream.
I think this alone will have impact, in terms of being able to reason about
CC behaviors.
Thanks,
--MM--
The best way to predict the future is to create it. - Alan Kay
We must not tolerate intolerance;
however our response must be carefully measured:
too strong would be hypocritical and risks spiraling out of
control;
too weak risks being mistaken for tacit approval.
On Sun, Jul 5, 2020 at 11:13 AM Jonathan Morton <chromatix99@gmail.com>
wrote:
> > 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
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2699 bytes --]
next prev parent reply other threads:[~2020-07-05 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 19:53 [Make-wifi-fast] IEEE 802.11n/ac Wireless Network Efficiency under different TCP Congestion Controls Dave Taht
2019-12-13 21:05 ` Carlo Augusto Grazia
2019-12-13 21:25 ` [Make-wifi-fast] the future belongs to pacing Dave Taht
2020-07-04 17:29 ` [Bloat] " Matt Mathis
[not found] ` <mailman.763.1593883755.24343.bloat@lists.bufferbloat.net>
2020-07-04 17:52 ` [Make-wifi-fast] " 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 ` [Make-wifi-fast] " Sebastian Moeller
2020-07-05 17:07 ` Matt Mathis
2020-07-05 17:29 ` [Make-wifi-fast] " Sebastian Moeller
2020-07-05 17:43 ` Michael Richardson
2020-07-05 18:09 ` Stephen Hemminger
2020-07-05 18:13 ` Jonathan Morton
2020-07-05 23:06 ` Matt Mathis [this message]
2020-07-06 14:08 ` [Make-wifi-fast] " Luca Muscariello
2020-07-06 14:14 ` [Make-wifi-fast] [Bloat] " Daniel Sterling
2020-07-06 17:01 ` Toke Høiland-Jørgensen
2019-12-13 21:09 ` [Make-wifi-fast] IEEE 802.11n/ac Wireless Network Efficiency under different TCP Congestion Controls Holland, Jake
2019-12-13 21:18 ` Carlo Augusto Grazia
2019-12-13 23:06 ` Dave Taht
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH56bmB+LFpDFmDDAcnJ1KA8=T62BiZ9jSKROd6EFcmRTO7Vwg@mail.gmail.com' \
--to=mattmathis@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=carloaugusto.grazia@unimore.it \
--cc=chromatix99@gmail.com \
--cc=jamshid@whatsapp.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--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