Sorry I'm not following well... Is this going to be implemented on both ath10k and ath10k-ct?
Cause on wave 1 devices, the non-ct version seems to do better in terms of throughput.
Cheers.
This has been implemented in non-CT since January snapshot builds, and CT since late March snapshot builds.
3 Likes
And I take it that, sadly, this didn't make it into 19.07.3?
Yes, it is not available in 19.07.3. It requires a minimum version of mac80211 backports 5.4.
19.07.X currently uses backports 4.19.
1 Like
I got rather busy reopening lupin lodge for the memorial day weekend and haven't got back on this. and today I hurt all over.
I did do a test deployment and at range we have problems. More details later, but do try it through a couple walls....
There have been a bunch of excellent, thorough benchmarks in this thread, but I haven't seen much in the way of real life usage results. Anyone want to share any impressions for real-life improvements with AQL for specific workloads (web browsing, gaming, video conferencing, whatever)? I realize that'd introduce a bit of subjectivity, but I'm curious.
My test deployment was in an area with a lot of 802.11ac wifi on the same base channel while I was running ht20, at a range of over 100meters. I got terrible throughput, and a lot of random - 2,2,2,2, then 100ms+ pings. Have no idea what was causing it to be that bad.
Sounds pretty challenging.... how's it do if you're at a closer distance like 15-30m?
My guess is that I have to stop using the base 36 or 153 channels entirely for HT20. Which I'll do.
The other problem with my test deployment was that I really needed to rip out the mods I'd made to the 2ghz portion of the patch and do it right. But at least it's deployed now and upgrading software less of a problem.
So I changed my patch to use 10ms for the target for 2ghz and 5 for the ath10k. I am still pretty sure we have multiple problems, but I'm firing off a build now and will test in the morning.
I see also there is a beta for a newer ath10k-ct version?
I've been using the ath10k-ct 6/3 dated firmware since it dropped and it's been stable, at least. I had a 10ms target build a little while back and it seemed to give me a better balance between latency and throughput than the 5ms target.
Ah, FWIW, interestingly enough I'm running a 6/4 snapshot on my C7 AP, compared with 19.07.2 and then 4/3 snap, its been fairly stable as well. No special build or other adjustments, just got the snapshot on that day. Have had maybe one or two of the momentary 2.4ghz dropout events, maybe less than prior builds. Not setup for serious testing. DSLReports looks pretty good, when I can get the bufferbloat results. Also no VOIP, or much videoconferencing out of the home network at this point, so can't compare there. Multi use case of TV watching, some gaming, wife doing VPN and video conferencing, etc... no complaints so far. Will ask my wife if she notices any differences with her VC, compared to earlier. Since there weren't much issues before, not a great test...
Forgive me for being a little foggy on how it goes, can I expect commits to end up in the daily snapshots fairly quickly or same day, or is there some delay? Guess right now I'm at least partly up to date, (except for patch changes) with my C7 on the above 6/4 snapshot running kmod-mac80211 4.19.123+5.7-rc3-1-2? Or not?
If you're running kmod-mac80211 4.19 that would indicate that you're running a 4.19 kernel, which does not have AQL. Your kmod versions should start with 5.4.
1 Like
For what it worth I just switched to the 5.4 kernel on my r7800 to try AQL and it's a huge improvement, really noticable with SSH sessions. Throughput is still fine too.
1 Like
Yeah, it's really rather remarkable the difference it makes on the r7800 (which I also have just as an AP). I was running some builds with a modified 5ms target that @dtaht was looking for input on. But at the moment I am running with default target time and it "feels" great on 5ghz (where 90%+ of my devices live).
@JonP Presently I am running kmod-mac80211 - 5.4.43+5.7-rc3-1-2
Sure it does. I've been running it for a few weeks now:
discus# head /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/xx:xx:xx:xx:xx/aql
Q depth: VO: 0 us VI: 0 us BE: 0 us BK: 0 us
Q limit[low/high]: VO: 5000/12000 VI: 5000/12000 BE: 5000/12000 BK: 5000/12000
discus# uname -r
4.19.123
I can't vouch for latest, but back at the end of March, Dave wrote:
I meant to thank Dave for his amazing work -- my ath10 was effectively useless before and I stuck on the ath9. Now it's wonderful.
1 Like
Do you see queues in the output of this command?
cat /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/aql
Ermm... @phelps just posted that output two posts up?
Anyway, I missed the memo on 4.19 but I stand corrected, thanks!