From: Michael Richardson <mcr@sandelman.ca>
To: Sebastian Moeller <moeller0@gmx.de>,
Matt Mathis <mattmathis@google.com>,
Carlo Augusto Grazia <carloaugusto.grazia@unimore.it>,
Jamshid Mahdavi <jamshid@whatsapp.com>,
bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] the future belongs to pacing
Date: Sun, 05 Jul 2020 13:43:27 -0400 [thread overview]
Message-ID: <14692.1593971007@localhost> (raw)
In-Reply-To: <9A7FBFF1-7F10-41DD-B5C3-5A45254CEB54@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Sebastian Moeller <moeller0@gmx.de> wrote:
> of the sending rate, no? BBRv2 as I understand it will happily run
> roughshod over any true rfc3168 AQM on the path, I do not have the
> numbers, but I am not fully convinced that typically the most
> significant throttling on a CDN to end-user path happens still inside
> the CDN's data center...
That's an interesting claim. I'm in no position to defend or refute it.
If it's true, though, it suggests some interesting solutions, because one can
more easily establish trust relationships within the data-center.
I'm specifically imagining a clock signal from the Top-of-Rack switch to the
senders.
Actually, it's not a clock, so much as a automotive style timing shaft
running down through all the 1-U servers, with fine vernier adjustments :-)
I'm also certain we've seen such technology before.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-05 17:43 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 [this message]
2020-07-05 18:09 ` Stephen Hemminger
2020-07-05 18:13 ` Jonathan Morton
2020-07-05 23:06 ` Matt Mathis
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=14692.1593971007@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=carloaugusto.grazia@unimore.it \
--cc=jamshid@whatsapp.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=mattmathis@google.com \
--cc=moeller0@gmx.de \
/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