From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] lower bounds for latency
Date: Fri, 5 Jun 2015 16:56:13 -0700 [thread overview]
Message-ID: <CAA93jw6RumDEeznJWemfh3-pxQB=RyzvmcMDb0tQw1uRtMwCSg@mail.gmail.com> (raw)
bob's been up to good stuff lately..
http://bobbriscoe.net/projects/latency/sub-mss-w.pdf
It was weird, only last night I was thinking upon the real lower
bounds on what was needed to keep a flow going in tcp at X,Y,Z rtts
(in the context of being dissatisified with the stanford result, and
not "quite" in the context of "buffering"), and he nails that in the
first paragraph.
Have to work through his prescription though....
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-06-05 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 23:56 Dave Taht [this message]
2015-06-06 1:02 ` David Lang
2015-06-06 1:58 ` Dave Taht
2015-06-06 3:08 ` David Lang
2015-06-06 11:15 ` Jonathan Morton
2015-06-12 19:09 Benjamin Cronce
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6RumDEeznJWemfh3-pxQB=RyzvmcMDb0tQw1uRtMwCSg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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