From: Johannes Berg <johannes@sipsolutions.net>
To: Julius Bairaktaris <julius@bairaktaris.de>
Cc: linux-wireless@vger.kernel.org, toke@toke.dk
Subject: Re: [PATCH] wifi: mac80211: scale the airtime queue limit by the station's weight
Date: Fri, 04 Sep 2026 12:07:02 +0200 [thread overview]
Message-ID: <b1fee6e45c4e2d215437f112c8819d74547ac11a.camel@sipsolutions.net> (raw)
In-Reply-To: <CAC1t37LF9Y=s23DNXmg9WM6sV+ENg+hTNgRNiW5ZMEwqx9CZJg@mail.gmail.com> (sfid-20260904_120304_814384_BD653DFA)
On Fri, 2026-09-04 at 10:02 +0000, Julius Bairaktaris wrote:
> > ath11k doesn't appear to use ieee80211_next_txq(), so it doesn't get
> > this and then AQL doesn't really work, I guess?
>
> ath11k is using the generic handler
>
> drivers/net/wireless/ath/ath11k/mac.c:
> .wake_tx_queue = ieee80211_handle_wake_tx_queue,
>
> which runs the ieee80211_next_txq() loop itself.
Oops, my bad.
> What is missing is
> the AQL feature bit and the airtime reporting, which my series on
> ath-next adds. The numbers in this patch were taken with that series
> applied, so AQL and the DRR were both active when the weight did
> nothing.
>
> > But for a driver that *does* use it, I believe this change is wrong.
>
> I agree with that. It would have to be gated so that drivers like
> ath9k don't get it.
Now I'm confused - I was thinking it'd be wrong _only_ for ath9k etc.,
but you just corrected me and said that ieee80211_next_txq() is called
anyway, so then wouldn't it also be wrong on ath11k? Or not wrong on
all?
> There is also the possibility of dropping this change and letting
> ath11k pass the weight to the firmware's own ATF, for which the WMI
> commands are already in wmi.h but unused. I haven't tested this yet,
> it's just a theory, but mac80211 would stay untouched. What do you
> think?
No idea, sorry.
johannes
next prev parent reply other threads:[~2026-09-04 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 14:24 [PATCH] wifi: mac80211: scale the airtime queue limit by the station's weight Julius Bairaktaris
2026-09-04 9:21 ` Johannes Berg
2026-09-04 9:46 ` Julius Bairaktaris
2026-09-04 9:49 ` Johannes Berg
2026-09-04 10:02 ` Julius Bairaktaris
2026-09-04 10:07 ` Johannes Berg [this message]
2026-09-04 10:35 ` Julius Bairaktaris
2026-09-04 11:46 ` Toke Høiland-Jørgensen
2026-09-08 13:52 ` Julius Bairaktaris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1fee6e45c4e2d215437f112c8819d74547ac11a.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=julius@bairaktaris.de \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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