From: Johannes Berg <johannes@sipsolutions.net>
To: "Michał Kazior" <michal.kazior@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 00/12] multi-channel support
Date: Fri, 23 Mar 2012 16:06:42 +0100 [thread overview]
Message-ID: <1332515202.10384.42.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1332514895.10384.40.camel@jlt3.sipsolutions.net> (sfid-20120323_160141_068030_63DCD1AC)
On Fri, 2012-03-23 at 16:01 +0100, Johannes Berg wrote:
> struct ieee80211_ops {
> ...
> void (*add_channel_context)(hw, ctx),
> void (*remove_channel_context)(hw, ctx),
> void (*change_channel_type)(hw, ctx),
> void (*assign_vif_channel_context)(hw, vif, ctx),
> };
And then we come full circle back to the queue mappings of course --
when the channel context is assigned, the driver is able to change the
queue details in the vif to map to whatever it needs, if anything
different. Like I said in the other email, some devices may use queues
for each interface regardless of channel (e.g. wl12xx, from discussions
with them) while others (ath9k at least, I suspect) would use queues per
channel context. For iwlwifi, I'm not sure yet.
johannes
next prev parent reply other threads:[~2012-03-23 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 12:21 [RFC 00/12] multi-channel support Michal Kazior
2012-03-23 9:29 ` Johannes Berg
2012-03-23 14:03 ` Michał Kazior
2012-03-23 14:31 ` Johannes Berg
2012-03-26 12:27 ` Michal Kazior
2012-03-26 12:45 ` Johannes Berg
2012-03-27 11:42 ` Michal Kazior
2012-03-27 11:59 ` Johannes Berg
2012-03-23 15:01 ` Johannes Berg
2012-03-23 15:06 ` Johannes Berg [this message]
2012-03-26 12:29 ` Michal Kazior
2012-03-26 13:19 ` Johannes Berg
2012-03-27 14:41 ` Michal Kazior
2012-03-27 15:00 ` Johannes Berg
2012-03-28 6:12 ` Michal Kazior
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=1332515202.10384.42.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
/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).