From: Matt Mathis <mattmathis@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Carlo Augusto Grazia <carloaugusto.grazia@unimore.it>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
jamshid@whatsapp.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] the future belongs to pacing
Date: Sat, 4 Jul 2020 10:29:02 -0700 [thread overview]
Message-ID: <CAH56bmCBSVFCfhcJxEdpX4yehqmPEE6qxkmXKA8=O_0PTr2Fng@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw40TT08WF9we18gYKPe9xcfhAskw6J5soey=riehV_90Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2975 bytes --]
Be aware that BBR is a moving target. There was an important WiFi fix
that went into BBRv1 in Jan 2019 that didn't make it into lots of
distros... BBRv2 is in the wings and fixes (nearly?) all sharing issues,
but isn't done yet.
Key takeaway: pacing is inevitable, because it saves large content
providers money (more efficient use of the most expensive silicon in the
data center, the switch buffer memory), however to use pacing we walk away
from 30 years of experience with TCP self clock, which is the foundation of
all of our CC research....
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 Fri, Dec 13, 2019 at 1:25 PM Dave Taht <dave.taht@gmail.com> wrote:
> and everything we know about the tcp macroscopic model, is obsolete,
> according to a provocative paper by matt mathis and Jamshid Mahdavi
> in sigcomm.
>
> https://ccronline.sigcomm.org/wp-content/uploads/2019/10/acmdl19-323.pdf
>
>
>
>
> On Fri, Dec 13, 2019 at 1:05 PM Carlo Augusto Grazia
> <carloaugusto.grazia@unimore.it> wrote:
> >
> > Hi Dave,
> > thank you for your email!
> > Toke told me about AQL a couple of weeks ago, I definitely want to test
> it ASAP.
> > BBR struggles a lot on Wi-Fi interfaces (ones with aggregation) with
> kernel 4.14 & 4.19.
> > Anyway, it seems that with BBRv2 on new kernels this problem does not
> exist anymore.
> >
> > Best regards
> > Carlo
> >
> > Il giorno ven 13 dic 2019 alle 20:54 Dave Taht <dave.taht@gmail.com> ha
> scritto:
> >>
> >> https://sci-hub.tw/10.1109/WiMOB.2019.8923418
> >>
> >> It predates the aql work, but the bbr result is puzzling.
> >>
> >>
> >> --
> >> Make Music, Not War
> >>
> >> Dave Täht
> >> CTO, TekLibre, LLC
> >> http://www.teklibre.com
> >> Tel: 1-831-435-0729 <(831)%20435-0729>
> >
> > --
> > --------------------------------------------------------------------
> > Carlo Augusto Grazia, Ph. D.
> > Assistant Professor
> > --------------------------------------------------------------------
> > Dept. of Engineering "Enzo Ferrari"
> > University of Modena and Reggio Emilia
> > Via Pietro Vivarelli, 10/1 - 41125 - Modena - Italy
> > Building 26, floor 2, room 28
> > Tel.: +39-059-2056323 <+39%20059%20205%206323>
> > email: carloaugusto.grazia@unimore.it
> > Link to my personal home page here
> > --------------------------------------------------------------------
>
>
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729 <(831)%20435-0729>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 4712 bytes --]
next prev parent reply other threads:[~2020-07-04 17:29 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 [this message]
[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
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='CAH56bmCBSVFCfhcJxEdpX4yehqmPEE6qxkmXKA8=O_0PTr2Fng@mail.gmail.com' \
--to=mattmathis@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=carloaugusto.grazia@unimore.it \
--cc=dave.taht@gmail.com \
--cc=jamshid@whatsapp.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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