From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH] mac80211: TDLS: fix skb queue/priority assignment
Date: Wed, 05 Sep 2018 14:32:05 +0200 [thread overview]
Message-ID: <87efe8yvju.fsf@toke.dk> (raw)
In-Reply-To: <1536147865.3528.14.camel@sipsolutions.net>
Johannes Berg <johannes@sipsolutions.net> writes:
> On Wed, 2018-09-05 at 13:41 +0200, Johannes Berg wrote:
>> On Wed, 2018-09-05 at 13:40 +0200, Toke H=C3=B8iland-J=C3=B8rgensen wrot=
e:
>> >=20
>> > Guess we'll have to deal with everything else if we ever move manageme=
nt
>> > frames onto the TXQ path as well...
>>=20
>> Depends on whether we care for management frame priorities or not ... so
>> far we haven't really.
>
> Actually, for the most part we have implemented that properly. Except
> for the TXQ I added for bufferable management ... oh well, I think we're
> the only user thereof now.
>
> I'm not sure we want to have a TXQ per TID for management, that seems
> overkill. But I'm also not sure how to solve this otherwise ...
Graft it to an existing TXQ, similar to how the fragments queue is used
now? Saves a TXQ at the expense of having to special-case it...
-Toke
next prev parent reply other threads:[~2018-09-05 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 11:34 [PATCH] mac80211: TDLS: fix skb queue/priority assignment Johannes Berg
2018-09-05 11:37 ` Johannes Berg
2018-09-05 11:40 ` Toke Høiland-Jørgensen
2018-09-05 11:41 ` Johannes Berg
2018-09-05 11:44 ` Johannes Berg
2018-09-05 12:32 ` Toke Høiland-Jørgensen [this message]
2018-09-05 12:33 ` Johannes Berg
2018-09-05 12:50 ` Toke Høiland-Jørgensen
2018-09-28 7:17 ` Johannes Berg
2018-09-28 9:04 ` 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=87efe8yvju.fsf@toke.dk \
--to=toke@toke.dk \
--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).