From: Johannes Berg <johannes@sipsolutions.net>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: support non-data TXQs
Date: Wed, 21 Jun 2017 09:09:19 +0200 [thread overview]
Message-ID: <1498028959.4955.1.camel@sipsolutions.net> (raw)
In-Reply-To: <c8637109-0292-23af-8bc6-8a7ba8e19595@quantenna.com>
On Tue, 2017-06-20 at 21:19 -0700, Igor Mitsyanko wrote:
> > - struct ieee80211_txq *txq[IEEE80211_NUM_TIDS];
> > + struct ieee80211_txq *txq[IEEE80211_NUM_TIDS + 1];
>
> Isn't that a little confusing? Wouldn't it be better to have a
> separate member for non-data txq and name it accordingly (something
> like txq_nodata).
We do this trick in quite a number of places, so it shouldn't really
come as a surprise.
> You have to handle it specially in most cases anyway I guess.
> With this approach you won't have to replace ARRAY_SIZE(sta->txq) by
> IEEE80211_NUM_TIDS anywhere.
Yeah, that would indeed be a good reason - I didn't realize the
ARRAY_SIZE() when I originally wrote the patch. And yes, I do need to
treat it specially - except then if it's separate I also have to
initialize it separately, so it's a bit of a trade-off.
> [snip]
[please trim the amount of text you quote]
> > - txqi->txq.ac = ieee80211_ac_from_tid(tid);
> > + if (tid == IEEE80211_NUM_TIDS + 1)
> > + txqi->txq.ac = IEEE80211_AC_VO;
>
> Why voice, maybe commit message should mention it?
That's standard for management frames, I really didn't think that'd
need any comment?
johannes
next prev parent reply other threads:[~2017-06-21 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:03 [RFC] mac80211: support non-data TXQs Johannes Berg
2017-06-20 21:09 ` Johannes Berg
2017-06-21 4:19 ` Igor Mitsyanko
2017-06-21 7:09 ` Johannes Berg [this message]
2017-06-21 7:38 ` Igor Mitsyanko
2017-06-21 8:36 ` Johannes Berg
2017-06-21 8:37 ` Johannes Berg
2017-06-21 8:48 ` Arend van Spriel
2017-06-21 9:14 ` Johannes Berg
2017-06-21 9:24 ` Johannes Berg
2017-06-21 9:45 ` Johannes Berg
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=1498028959.4955.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
/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.