From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Alexander Wetzel <alexander@wetzel-home.de>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>,
Alexander Wetzel <alexander@wetzel-home.de>
Subject: Re: [PATCH] mac80211: Simplify queue selection
Date: Tue, 10 May 2022 20:25:31 +0200 [thread overview]
Message-ID: <8735hhxn1g.fsf@toke.dk> (raw)
In-Reply-To: <20220510155828.9406-1-alexander@wetzel-home.de>
Alexander Wetzel <alexander@wetzel-home.de> writes:
> I still don't understand why we don't want to use qdisc with the iTXQ
> drivers. I now just made sure we don't start using qdiscs with this
> patch to start with the least invasive approach. Anyone able to shed
> some light on that?
Because of aggregation, basically. To build an aggregate you need to be
able to pull several packets that has the same STA+TID; if all packets
on the interface are just sitting in a qdisc you have no interface to do
this.
Before switching to TXQs, drivers (the ath9k in particular) would solve
this by having another layer of per-sta queueing inside the driver,
which was just a dump FIFO that added a bunch of latency. The iTXQs
moved that up to mac80211, while doing proper queue management (flow
queueing + CoDel derived from the FQ-CoDel qdisc) at the same time; this
made the qdisc layer redundant for most purposes, which is why we
switched to noqueue by default.
-Toke
prev parent reply other threads:[~2022-05-10 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:58 [PATCH] mac80211: Simplify queue selection Alexander Wetzel
2022-05-10 16:10 ` Felix Fietkau
2022-05-10 16:13 ` Alexander Wetzel
2022-05-10 16:21 ` Felix Fietkau
2022-05-10 16:22 ` Johannes Berg
2022-05-15 11:10 ` Alexander Wetzel
2022-05-10 18:26 ` Toke Høiland-Jørgensen
2022-05-10 19:06 ` Johannes Berg
2022-05-10 19:27 ` Toke Høiland-Jørgensen
2022-05-10 18:25 ` Toke Høiland-Jørgensen [this message]
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=8735hhxn1g.fsf@toke.dk \
--to=toke@kernel.org \
--cc=alexander@wetzel-home.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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;
as well as URLs for NNTP newsgroup(s).