[Make-wifi-fast] mesh deployment with ath9k driver changes

[Pete Heist]

> On Jul 5, 2018, at 7:37 PM, Toke Høiland-Jørgensen <toke at toke.dk> wrote:
> 
> Pete Heist <pete at heistp.net> writes:
> 
>>> On Jul 5, 2018, at 3:08 PM, Toke Høiland-Jørgensen <toke at toke.dk> wrote:
>>> 
>>> Pete Heist <pete at heistp.net> writes:
>>> 
>>>> And in the aqm driver support I’m not sure what fq_overmemory
>>>> signifies (Toke may know that) or if the other stats are within the
>>>> expected ranges for this amount of traffic.
>>> 
>>> Overmemory is the amount of times the total queue size went over the
>>> 4MiB limit. So I'd say that 60 million times is...quite a lot. Is there
>>> a lot of traffic that doesn't respond to congestion signals on that
>>> link?
>> 
>> Wow, ok. Well, I suspect it’s p2p.
> 
> Wouldn't be surprised. Note that packets will be dropped from the
> longest queue, though, so unresponsive flows just hurt themselves...

Probably not before they’ve wasted airtime though and and impacted everyone else...