From: Johannes Berg <johannes@sipsolutions.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Eliad Peller <eliad@wizery.com>, Jouni Malinen <j@w1.fi>
Subject: Re: mac80211 queue handling in multi-channel
Date: Mon, 27 Feb 2012 16:46:15 +0100 [thread overview]
Message-ID: <1330357575.3483.57.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAGXE3d_SNsrA-KLuPVe_TWnbaVGK3ABr_4TWbtJWU568=BgWbw@mail.gmail.com> (sfid-20120227_163842_268823_6D7AF64F)
On Mon, 2012-02-27 at 16:38 +0100, Helmut Schaa wrote:
> On Mon, Feb 27, 2012 at 12:49 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > Then of course, the driver needs to tell mac80211 about queue mapping.
> > For this, there's one global queue:
> > * off-channel TX queue
> > Additionally, there are per-interface queues:
> > * 4 per AC
> > * CAB for this interface
>
> Ralink devices have only the 4 hw queues and no CAB queue. So, would
> each interface point to the same hw queue or would the driver have to do
> some sort of translation?
No, just like today I'd expect each interface to point to the same hw
queue. In fact, even in devices that do have more queues I would expect
multiple interfaces to point to the same hw queue, if they share
channels.
This will be somewhat tricky when an the mapping isn't static, but for
that the netdev queues can be stopped and then the reassignment is
probably not so much of a problem.
> Also Ralink devices don't have a CAB queue :)
You just said that ;-)
But in that case I suppose the CAB queue would simply point to the BE
queue or so as well. But I think they are also quite broken wrt. sending
multicast-after-DTIM anyway, no? In any case I'd then expect this to
either point to a "virtual" queue that the driver simply has in
software, or to the real BE queue, depending on the desired queue-full
semantics.
johannes
next prev parent reply other threads:[~2012-02-27 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 11:49 mac80211 queue handling in multi-channel Johannes Berg
2012-02-27 15:10 ` Dave Taht
2012-02-27 15:29 ` Dave Taht
2012-02-27 15:42 ` Johannes Berg
2012-02-27 15:38 ` Helmut Schaa
2012-02-27 15:46 ` Johannes Berg [this message]
2012-02-27 15:49 ` Helmut Schaa
2012-03-26 16:13 ` Johannes Berg
2012-03-26 17:03 ` Richard Farina
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=1330357575.3483.57.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=helmut.schaa@googlemail.com \
--cc=j@w1.fi \
--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 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).