From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] bufferbloat and beyond
Date: Wed, 9 Jun 2021 06:35:52 -0700 [thread overview]
Message-ID: <D312FD8C-3FF6-4209-A15C-8287495275EB@teklibre.net> (raw)
for those of you here that hasn’t
read it yet, toke phd thesis was the first in history to have every line of code and every API put into the linux kernel before he graduated.
https://bufferbloat-and-beyond.net/
The most important papers in it are “ending the anomaly” - how we fixed wifi - and the one on cake. Skip to the pretty graphs if you are low on time...
reply other threads:[~2021-06-09 13:35 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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D312FD8C-3FF6-4209-A15C-8287495275EB@teklibre.net \
--to=davet@teklibre.net \
--cc=starlink@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