From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] PCC: Re-architecting Congestion Control for Consistent High Performance [pdf]
Date: Thu, 2 Oct 2014 10:59:45 -0700 [thread overview]
Message-ID: <CAA93jw5Y3KrLf8OS14gdje_XsqzmF0vEddHp2RLQnnd5Joh8_w@mail.gmail.com> (raw)
I read this paper a while back but was discouraged at the lack of
source code. They did do a good job of describing the parameter space
a TCP needs to work in, and was worth reading just for that.
Some code... and John Nagle! surfaced on this thread:
https://news.ycombinator.com/item?id=8381480
--
Dave Täht
https://www.bufferbloat.net/projects/make-wifi-fast
reply other threads:[~2014-10-02 17:59 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=CAA93jw5Y3KrLf8OS14gdje_XsqzmF0vEddHp2RLQnnd5Joh8_w@mail.gmail.com \
--to=dave.taht@gmail.com \
--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