From: Johannes Berg <johannes@sipsolutions.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>, linux-wireless@vger.kernel.org
Cc: make-wifi-fast@lists.bufferbloat.net, Felix Fietkau <nbd@nbd.name>
Subject: Re: [Make-wifi-fast] [RFC v2 2/4] mac80211: Add airtime accounting and scheduling to TXQs
Date: Wed, 29 Aug 2018 09:44:18 +0200 [thread overview]
Message-ID: <1535528658.5215.19.camel@sipsolutions.net> (raw)
In-Reply-To: <153115422499.7447.2570671473822724496.stgit@alrua-x1> (sfid-20180709_183717_542396_91AD1C0D)
On Mon, 2018-07-09 at 18:37 +0200, Toke Høiland-Jørgensen wrote:
>
> @@ -427,6 +428,8 @@ struct sta_info *sta_info_alloc(struct ieee80211_sub_if_data *sdata,
> sta->cparams.interval = MS2TIME(100);
> sta->cparams.ecn = true;
>
> + sta->airtime.weight = 1;
Perhaps it might be useful to start with a higher default (even
something like 1<<8) as that would allow adjusting up/down single
stations, without having to adjust all stations and listening to new
additions to adjust them quickly etc?
Theoretically this doesn't really matter, but from a practical POV it
may be easier to leave them all at the default and just adjust the ones
that need adjustment for some reason.
> ieee80211_sta_register_airtime
Do we really need this? We already have at least TX status with airtime,
for ieee80211_sta_tx_notify() and friends, and the station pointer in
that context, so couldn't we piggy-back on this? At least WMM-AC already
requires the driver to provide this.
johannes
next prev parent reply other threads:[~2018-08-29 7:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:37 [Make-wifi-fast] [RFC v2 0/4] Move TXQ scheduling into mac80211 Toke Høiland-Jørgensen
2018-07-09 16:37 ` [Make-wifi-fast] [RFC v2 1/4] mac80211: Add TXQ scheduling API Toke Høiland-Jørgensen
2018-07-11 0:14 ` Rajkumar Manoharan
2018-07-11 20:48 ` Toke Høiland-Jørgensen
2018-07-12 22:40 ` Rajkumar Manoharan
2018-07-12 23:13 ` Toke Høiland-Jørgensen
2018-07-13 0:33 ` Rajkumar Manoharan
2018-07-13 13:39 ` Toke Høiland-Jørgensen
2018-07-17 1:06 ` Rajkumar Manoharan
2018-07-19 14:18 ` Toke Høiland-Jørgensen
2018-07-21 1:01 ` Rajkumar Manoharan
2018-07-21 20:54 ` Toke Høiland-Jørgensen
2018-07-24 0:42 ` Rajkumar Manoharan
2018-07-24 11:08 ` Toke Høiland-Jørgensen
2018-07-30 21:10 ` Rajkumar Manoharan
2018-07-30 22:48 ` Toke Høiland-Jørgensen
2018-07-31 0:19 ` Rajkumar Manoharan
2018-08-29 7:36 ` Johannes Berg
2018-08-29 9:22 ` Toke Høiland-Jørgensen
2018-08-29 9:24 ` Johannes Berg
2018-08-29 10:09 ` Toke Høiland-Jørgensen
2018-07-09 16:37 ` [Make-wifi-fast] [RFC v2 2/4] mac80211: Add airtime accounting and scheduling to TXQs Toke Høiland-Jørgensen
2018-08-29 7:44 ` Johannes Berg [this message]
2018-08-29 9:27 ` Toke Høiland-Jørgensen
2018-08-29 10:14 ` Johannes Berg
2018-08-29 10:33 ` Toke Høiland-Jørgensen
2018-08-29 10:40 ` Johannes Berg
2018-08-29 14:16 ` Toke Høiland-Jørgensen
2018-07-09 16:37 ` [Make-wifi-fast] [RFC v2 4/4] ath9k: Switch to mac80211 TXQ scheduling and airtime APIs Toke Høiland-Jørgensen
2018-07-09 16:37 ` [Make-wifi-fast] [RFC v2 3/4] cfg80211: Add airtime statistics and settings Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1535528658.5215.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nbd@nbd.name \
--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