From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Cc: jacklee@computer.org, BBR Development <bbr-dev@googlegroups.com>
Subject: [Bloat] flash tcp paper
Date: Fri, 17 Dec 2021 02:51:33 -0800 [thread overview]
Message-ID: <CAA93jw7g7MBcQHYYV=LiY1c=hb44BbOnO4R9nR-0xyxr8qsjmA@mail.gmail.com> (raw)
There's a lot to like about this paper,
https://www.sci-hub.se/10.1109/ACCESS.2021.3077612
Not least of which they supply source code for it,
https://github.com/mclab-cuhk/TCP-FLASH
and focus on improving slow start, and try to use values for rtt and
buffering (30ms) that they think representative of the technologies
they think they are testing. The loss model is kind of bogus, though
for wifi and lte, I think, and I keep wishing a new tcp developer
would try them out also against docsis-pie and fq-codel.
--
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
reply other threads:[~2021-12-17 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw7g7MBcQHYYV=LiY1c=hb44BbOnO4R9nR-0xyxr8qsjmA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jacklee@computer.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