From: Dave Taht <dave.taht@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] splat start?
Date: Sat, 9 May 2015 19:18:36 -0700 [thread overview]
Message-ID: <CAA93jw5xKvVxHh-DZZu0rRdDFF424hZevwG9xSci1OHoa0jGOw@mail.gmail.com> (raw)
One of the things bugging me lately is that we actually have a lot of
forms of "slow start"
on the table - HyStart, Initial Spreading, reno vs cubic, dctcp, IW2,
IW4, IW10, TSO offloads, the effect of GRO on it, etc. I dont know
what is in QUIC, either.
I would love a comprehensive guide to exactly the behaviors of "slow
start" in every tcp known to man and some sane way to refer to them
all in a cross reference and a spreadsheet.
Does something like that exist? Just the "* start" behavior.
The world has spent way too much time analyzing congestion avoidance mode.
--
Dave Täht
next reply other threads:[~2015-05-10 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 2:18 Dave Taht [this message]
[not found] ` <C1B5186C-B66F-4BA4-BFF7-5ED02C21F932@tik.ee.ethz.ch>
2015-05-11 17:38 ` [Bloat] [aqm] " 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/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=CAA93jw5xKvVxHh-DZZu0rRdDFF424hZevwG9xSci1OHoa0jGOw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@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