From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Make - fast - wifi project plan review from 2014....
Date: Fri, 18 Sep 2020 09:05:43 -0700 [thread overview]
Message-ID: <CAA93jw4Ad4LVWxouqa9BG4PzMBFVvYfTuR62co4PV2D9UyYXUQ@mail.gmail.com> (raw)
I recently had cause to go review the original make-wifi-fast project
plan ( https://docs.google.com/document/d/1Se36svYE1Uzpppe1HWnEyat_sAGghB3kE285LElJBW4/edit)
(and related presentation:
https://www.youtube.com/watch?v=Rb-UnHDw02o&t=25m30s had the fun bit)
I'm glad that since that time ATF and mesh networking became
realities, fq_codel and per station queuing gained support in various
products, and AQL started to work on ath10k, but I'm pretty sure
things in that document like rate and power aware scheduling
(minstrel-bluse), excessive counter based hw retries, and other
problems we identified back then are still problems, not to mention
the recent ofdma work....
I have been observing pretty bad behavior with a lot of 802.11ac
access points around, (recently one that
went 4Mbits over 40 feet through glass outdoors, but 600 indoors and
10 feet) but have nothing but guesses as to the causes. Infinite
retries? Everything on 160 mhz wide channels?
Has there been any good news or good tools lately?
I pulled my ax200s out of the box and was going to see if there was
any progress there.
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next reply other threads:[~2020-09-18 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 16:05 Dave Taht [this message]
2020-09-18 20:58 ` Jonathan Foulkes
2020-09-19 7:33 ` Bob McMahon
2020-09-19 10:40 ` Toke Høiland-Jørgensen
2020-09-19 18:11 ` Bob McMahon
[not found] <mailman.0.1600531202.4968.make-wifi-fast@lists.bufferbloat.net>
2020-09-25 7:24 ` Jon Pike
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4Ad4LVWxouqa9BG4PzMBFVvYfTuR62co4PV2D9UyYXUQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--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