On Mon, Nov 19, 2018 at 3:30 PM Simon Barber <simon@xxxxxxxxxxxxxx> wrote: > > > > On Nov 19, 2018, at 2:44 PM, Toke Høiland-Jørgensen <toke@xxxxxxx> wrote: > > Dave Taht <dave@xxxxxxxx> writes: > > Toke Høiland-Jørgensen <toke@xxxxxxx> writes: > > Felix Fietkau <nbd@xxxxxxxx> 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. http://blog.cerowrt.org/post/dql_on_wifi_2/ 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. > Simon > > _______________________________________________ > Make-wifi-fast mailing list > Make-wifi-fast@xxxxxxxxxxxxxxxxxxxxx > https://lists.bufferbloat.net/listinfo/make-wifi-fast -- Dave Täht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740
