[Make-wifi-fast] [PATCH v3 3/6] mac80211: Add airtime accounting and scheduling to TXQs
dave.taht at gmail.com
Mon Nov 19 18:47:05 EST 2018
On Mon, Nov 19, 2018 at 3:30 PM Simon Barber <simon at superduper.net> wrote:
> On Nov 19, 2018, at 2:44 PM, Toke Høiland-Jørgensen <toke at toke.dk> wrote:
> Dave Taht <dave at taht.net> writes:
> Toke Høiland-Jørgensen <toke at toke.dk> writes:
> Felix Fietkau <nbd at nbd.name> writes:
> On 2018-11-14 18:40, Toke Høiland-Jørgensen wrote:
> This part doesn't really make much sense to me, but maybe I'm
> misunderstanding how the code works.
> Let's assume we have a driver like ath9k or mt76, which tries to keep a
> Well, there's going to be a BQL-like queue limit (but for airtime) on
> top, which drivers can opt-in to if the hardware has too much queueing.
> Very happy to read this - I first talked to Dave Taht about the need for Time Queue Limits more than 5 years ago!
Michal faked up a dql estimator 3 (?) years ago. it worked.
As a side note, in *any* real world working mu-mimo situation at any
scale, on any equipment, does anyone have any stats on how often the
feature is actually used and useful?
My personal guess, from looking at the standard, was in home
scenarios, usage would be about... 0, and in a controlled environment
in a football stadium, quite a lot.
In a office or apartment complex, I figured interference and so forth
would make it a negative benefit due to retransmits.
I felt when that part of the standard rolled around... that mu-mimo
was an idea that should never have escaped the lab. I can be convinced
by data, that we can aim for a higher goal here. But it would be
comforting to have a measured non-lab, real-world, at real world
rates, result for it, on some platform, of it actually being useful.
> Make-wifi-fast mailing list
> Make-wifi-fast at lists.bufferbloat.net
CTO, TekLibre, LLC
More information about the Make-wifi-fast