From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: David Lang <david@lang.hm>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] what is the state of the airtime fairness patches?
Date: Wed, 17 Jan 2018 11:48:31 +0100 [thread overview]
Message-ID: <87efmovk00.fsf@toke.dk> (raw)
In-Reply-To: <alpine.DEB.2.02.1801161727030.21503@nftneq.ynat.uz>
David Lang <david@lang.hm> writes:
> I'm getting ready to finalize the build for the Scale conference, is airtime
> fairness upstream in LEDE for both ath9 and ath10?
>
> Has it been ported to anything else?
Airtime fairness is upstream in both mainline and LEDE for ath9k. There
have been some preliminary developments for ath10k (looks like we can
get the data we need), but nothing that works yet. Should be possible to
get it to work for mt76 as well, at least.
The fq_codel-based queueing stuff is active for both ath9k, ath10k and
mt76, though.
> Is there anything you would like me to gather in this environment?
Hmm, things that might be interesting:
- Distribution of client capabilities (5/2.4Ghz, MIMO mode, n/ac,
achieved rates, etc. - however much data you can reasonably gather)
- Lasthop latency experienced by the clients (you could get this by
capturing TCP handshakes and measuring the ACK-SYNACK delay, as shown
in Figure 1 of this paper:
https://dl.acm.org/citation.cfm?doid=2999572.2999603) - this could
give an indication of bloat in the client drivers.
- QoS usage (how much traffic is sent on each of the VO/VI/BE/BK
queues).
> I've got a lot of the wndr3700/3800 APs (ath9k) and would like to get
> a handful of -ac devices to see if there are enough users who would
> take advantage of the higher speeds to matter.
I think we are getting to the point where ac is fairly common, at least
in phones. But data on this would be good of course :)
-Toke
next prev parent reply other threads:[~2018-01-17 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 1:43 David Lang
2018-01-17 10:48 ` Toke Høiland-Jørgensen [this message]
2018-01-19 9:58 ` Toke Høiland-Jørgensen
2018-02-11 20:25 ` David Lang
2018-03-16 16:53 ` Dave Taht
2018-04-17 21:10 Bruno George Moraes
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=87efmovk00.fsf@toke.dk \
--to=toke@toke.dk \
--cc=david@lang.hm \
--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