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: [RFC v2 1/4] mac80211: Add TXQ scheduling API
Date: Wed, 29 Aug 2018 11:24:38 +0200 [thread overview]
Message-ID: <1535534678.5215.23.camel@sipsolutions.net> (raw)
In-Reply-To: <87a7p54jed.fsf@toke.dk>
On Wed, 2018-08-29 at 11:22 +0200, Toke Høiland-Jørgensen wrote:
> > We're also working on adding a TXQ for (bufferable) management packets
> > - I wonder how that should interact here? Always be scheduled first?
>
> Ah, cool! It may be that it should be given priority, yeah. Presently,
> the multicast queue just rotates in the RR with the others, but is never
> throttled as it doesn't have an airtime measure (though perhaps it
> should)? But that might not be desirable for management frames, as
> presumable those need to go out as fast as possible?
Good question. I guess the multicast should have an airtime measure, but
I don't think we want to do accounting on the management. That really
should be few frames, and we want them out ASAP in most cases.
> Hmm, I seem to recall thinking about just putting the call to
> schedule_txq() into drv_wake_tx_queue; don't remember why I ended up
> dropping that; but will take another look at whether it makes sense to
> combine things.
I was thinking the other way around - but that doesn't work since you'd
loop from the driver to itself. This way might work, I guess, hadn't
considered that.
Might be better anyway though to make a new inline that does both, since
the drv_() calls usually really don't do much on their own (other than
checks, and in one case backward compatibility code, but still)
johannes
next prev parent reply other threads:[~2018-08-29 13:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:37 [RFC v2 0/4] Move TXQ scheduling into mac80211 Toke Høiland-Jørgensen
2018-07-09 16:37 ` [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 [this message]
2018-08-29 10:09 ` Toke Høiland-Jørgensen
2018-07-09 16:37 ` [RFC v2 3/4] cfg80211: Add airtime statistics and settings Toke Høiland-Jørgensen
2018-07-09 16:37 ` [RFC v2 4/4] ath9k: Switch to mac80211 TXQ scheduling and airtime APIs Toke Høiland-Jørgensen
2018-07-09 16:37 ` [RFC v2 2/4] mac80211: Add airtime accounting and scheduling to TXQs Toke Høiland-Jørgensen
2018-08-29 7:44 ` Johannes Berg
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
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=1535534678.5215.23.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.