From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net,
Johannes Berg <johannes@sipsolutions.net>
Subject: [Make-wifi-fast] less latency, more filling... for wifi
Date: Mon, 9 Oct 2017 13:13:18 -0700 [thread overview]
Message-ID: <CAA93jw6afzp=dNKmxGoT-v3pqT-DztEypQK3s8BJB5m7aKyZNg@mail.gmail.com> (raw)
There were five ideas I'd wanted to pursue at some point. I''m not
presently on linux-wireless, nor do I have time to pay attention right
now - but I'm enjoying that thread passively.
To get those ideas "out there" again:
* adding a fixed length fq'd queue for multicast.
* Reducing retransmits at low rates
See the recent paper:
"Resolving Bufferbloat in TCP Communication over IEEE 802.11 n WLAN by
Reducing MAC Retransmission Limit at Low Data Rate" (I'd paste a link
but for some reason that doesn't work well)
Even with their simple bi-modal model it worked pretty well.
It also reduces contention with "bad" stations more automagically.
* Less buffering at the driver.
Presently (ath9k) there are two-three aggregates stacked up at the driver.
With a good estimate for how long it will take to service one, forming
another within that deadline seems feasible, so you only need to have
one in the hardware itself.
Simple example: you have data in the hardware projected to take a
minimum of 4ms to transmit. Don't form a new aggregate and submit it
to the hardware for 3.5ms.
I know full well that a "good" estimate is hard, and things like
mu-mimo complicate things. Still, I'd like to get below 20ms of
latency within the driver, and this is one way to get there.
* Reducing the size of a txop under contention
if you have 5 stations getting blasted away at 5ms each, and one that
only wants 1ms worth of traffic, "soon", temporarily reducing the size
of the txop for everybody so you can service more stations faster,
seems useful.
* Merging acs when sane to do so
sane aggregation in general works better than prioritizing does, as
shown in ending the anomaly.
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2017-10-09 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 20:13 Dave Taht [this message]
2017-10-09 20:41 ` dpreed
2017-10-09 21:04 ` Bob McMahon
2017-10-09 21:44 ` Simon Barber
2017-10-09 22:02 ` Bob McMahon
2017-10-11 20:03 ` Bob McMahon
2017-10-16 21:26 ` Simon Barber
2017-10-17 4:53 ` Bob McMahon
2017-10-11 21:30 ` Jesper Dangaard Brouer
2017-10-12 8:32 ` Toke Høiland-Jørgensen
2017-10-12 18:51 ` Bob McMahon
2017-10-13 9:28 ` Toke Høiland-Jørgensen
2017-10-13 18:47 ` Bob McMahon
2017-10-13 19:41 ` Bob McMahon
2017-10-14 1:46 ` Bob McMahon
[not found] <mailman.778.1507581712.3609.make-wifi-fast@lists.bufferbloat.net>
2017-10-16 18:28 ` Pete Heist
2017-10-16 19:56 ` Dave Taht
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='CAA93jw6afzp=dNKmxGoT-v3pqT-DztEypQK3s8BJB5m7aKyZNg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=johannes@sipsolutions.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