From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/9] rt2x00: Use rt2x00 queue numbering
Date: Mon, 21 Apr 2008 19:30:31 +0200 [thread overview]
Message-ID: <200804211930.31340.IvDoorn@gmail.com> (raw)
In-Reply-To: <1208798232.26186.121.camel@johannes.berg>
On Monday 21 April 2008, Johannes Berg wrote:
> Hi Ivo,
>
> On Mon, 2008-04-21 at 19:00 +0200, Ivo van Doorn wrote:
> > Use the rt2x00 queue enumeration as much as possible,
> > removing the usage of the mac80211 queue numbering
> > wherever it is possible.
> >
> > This makes it easier for mac80211 to change it queue
> > identification scheme without having to deal with
> > big changes in the rt2x00 code.
>
> Cool, thanks a lot. One small note:
>
> > +static inline enum data_queue_qid mac80211_queue_to_qid(unsigned int queue)
> > +{
> > + /* Regular TX queues are mapped directly */
> > + if (queue < NUM_TX_DATA_QUEUES)
> > + return queue;
> > + else if (queue == IEEE80211_TX_QUEUE_BEACON)
> > + return QID_BEACON;
> > + else if (queue == IEEE80211_TX_QUEUE_AFTER_BEACON)
> > + return QID_ATIM;
> > + return QID_OTHER;
>
> Are you actually using TX_QUEUE_AFTER_BEACON? That queue number is a
> historical accident (imho) and not used, we actually use the
> IEEE80211_TXCTL_SEND_AFTER_DTIM tx control flag.
Actually both the checks for IEEE80211_TX_QUEUE_BEACON and IEEE80211_TX_QUEUE_AFTER_BEACON
are fake and only present for completeness.
rt2x00 does check for IEEE80211_TXCTL_SEND_AFTER_DTIM and will resolve it to QID_ATIM
if that queue is supported by the hardware (rt2400pci and rt2500pci) and resolves it to the control->queue
in all other cases.
> Also, with the QoS patch, those queue numbers should finally go away and
> mac80211 will not pass anything but the data queues, hence, this small
> inline would probably be reduced to "return queue;" by the patch.
This function only exists to move the translation in a single location.
When the translation isn't needed anymore because skb_get_queue_mapping(skb)
or something else is used, then this function can be removed completely. :)
Ivo
next prev parent reply other threads:[~2008-04-21 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804211858.46659.IvDoorn@gmail.com>
2008-04-21 16:59 ` [PATCH 1/9] rt2x00: Support hardware RTS and CTS-to-self frames Ivo van Doorn
2008-04-21 16:59 ` [PATCH 2/9] rt2x00: Remove DRIVER_SUPPORT_MIXED_INTERFACES Ivo van Doorn
2008-04-21 17:00 ` [PATCH 3/9] rt2x00: Don't enable short preamble for 1MBs Ivo van Doorn
2008-04-21 17:00 ` [PATCH 4/9] rt2x00: Use rt2x00 queue numbering Ivo van Doorn
2008-04-21 17:17 ` Johannes Berg
2008-04-21 17:30 ` Ivo van Doorn [this message]
2008-04-21 17:58 ` Ivo van Doorn
2008-04-21 17:56 ` Johannes Berg
2008-04-21 21:40 ` Ivo van Doorn
2008-04-21 17:01 ` [PATCH 5/9] rt2x00: Fix quality/activity led handling Ivo van Doorn
2008-04-21 17:01 ` [PATCH 6/9] rt2x00: Clarify supported chipsets in Kconfig Ivo van Doorn
2008-04-21 17:01 ` [PATCH 7/9] rt2x00: Add helper macros Ivo van Doorn
2008-04-21 17:02 ` [PATCH 8/9] rt2x00: Fix kernel-doc Ivo van Doorn
2008-04-21 17:02 ` [PATCH 9/9] rt2x00: Release rt2x00 2.1.5 Ivo van Doorn
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=200804211930.31340.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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.