From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] the last big make-wifi-fast talk I gave
Date: Thu, 30 Apr 2020 09:21:32 -0700 [thread overview]
Message-ID: <CAA93jw7RL+_37z5-=s0=_dQBQAWA=qpJFDT90uJC=9oVX9xNow@mail.gmail.com> (raw)
Since we have accumulated more than a few new people on the list...
Back in 2016, I explained much that was wrong with wifi here, and at
this particular time in the talk, I explained one of the biggest
things wrong with 802.11n, ac, and ax, packet aggregation, and how the
entire industry did testing, using my often hilarious
method of "people as packets"....
https://www.youtube.com/watch?v=Rb-UnHDw02o&t=25m22s
there was a LOT more wrong with wifi that could be fixed also outlined
in that talk (multicast, 802.11e stupidities, etc - see the talk),
but just fixing queueing as well as we did exhausted all the resources
we had and it still took 4 years to get AQL into a more deployable
state.
Blatant plug: Toke's thesis is now in its second print edition and
available for either download or a paper copy at:
https://bufferbloat-and-beyond.net/
Get a copy. Get 10 copies! Give em to an IT manager, CTO, sysadmin,
network designer, network operator, anyone that might listen. Post on
your favorite social media site. Put one in your bathroom to read when
you need a break from the internet itself.
I gave a talk over here at broadcom about how to make queuing better
in general, but I don't think they listened.
http://flent-fremont.bufferbloat.net/~d/broadcom_aug9.pdf
I'm pretty sure the next gen802.11ax mt76 chip can do gang scheduling
right for ofdma, not so sure about anything else.
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
reply other threads:[~2020-04-30 16:21 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7RL+_37z5-=s0=_dQBQAWA=qpJFDT90uJC=9oVX9xNow@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@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