From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
bloat-announce@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
codel@lists.bufferbloat.net
Subject: Video of my talk at MIT "What's Wrong with WiFi?" is up
Date: Fri, 15 Feb 2013 11:45:04 -0800 [thread overview]
Message-ID: <CAA93jw6Z4u9aO_RPhSir1k6N=GZ44aoo26NQ2azTbS8g-utnyw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
http://www.youtube.com/watch?v=Wksh2DPHCDI&feature=youtu.be
the first half of this talk revises and extends on the previous talk at
stanford (where I mostly talk about fq_codel, and RRUL). In particular I
extended the slide set to include more examples, and have a rather killer
one showing vast improvements in web page completion time, under load, with
fq_codel..
The second half of the MIT goes into my take on some of what's going wrong
with wifi.
In the MIT talk, I take some time to talk about my plans for the wifi
yurtlab testbed this summer, as well. I am entertaining proposals as to
what else to do with it. If anybody has
ideas/algorithms/hardware/time/funding/resources for this effort, please
speak up!
The second half of the stanford talk (2 weeks ago) went into detail on
codel and fq_codel, and the audio to it was just improved rather radically,
so if you haven't seen that one, slides and video are at:
http://netseminar.stanford.edu/
I hope that the methods I'm using to describe network behavior (RRUL), and
codel/fq_codel's behavior continue to improve to where one day they can be
used to effectively illustrate an article or two. In the interim, I keep
trying talks and getting feedback on what's getting through, or not. Enjoy.
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 1646 bytes --]
reply other threads:[~2013-02-15 19:45 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6Z4u9aO_RPhSir1k6N=GZ44aoo26NQ2azTbS8g-utnyw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-announce@lists.bufferbloat.net \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@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