From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Bloat] uplink bufferbloat and scheduling problems
Date: Tue, 30 Nov 2021 16:13:56 -0800 [thread overview]
Message-ID: <CAA93jw48R8YfCR6TPWwdsDPA1=gzJjRMKo6c0nxfWvKt1ws0tQ@mail.gmail.com> (raw)
Money quote: "Figure 2a is a good argument to focus latency
research work on downlink bufferbloat."
It peaked at 1.6s in their test:
https://hal.archives-ouvertes.fr/hal-03420681/document
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2021-12-01 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 0:13 Dave Taht [this message]
2021-12-01 20:26 ` [Bloat] [Cerowrt-devel] " David P. Reed
2021-12-01 21:06 ` David Lang
2021-12-01 21:09 ` David Lang
2021-12-01 22:28 ` Valdis Klētnieks
2021-12-02 0:10 ` Toke Høiland-Jørgensen
2021-12-02 9:09 ` David Lang
2021-12-02 17:20 ` Dave Collier-Brown
2021-12-02 19:33 ` David Lang
2021-12-02 8:11 ` Jan Ceuleers
2021-12-02 8:45 ` Sebastian Moeller
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='CAA93jw48R8YfCR6TPWwdsDPA1=gzJjRMKo6c0nxfWvKt1ws0tQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@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