From: Michal Kazior <michal.kazior@tieto.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v3] initial channel context implementation
Date: Wed, 27 Jun 2012 09:30:32 +0200 [thread overview]
Message-ID: <4FEAB698.5070309@tieto.com> (raw)
In-Reply-To: <1340718188.14634.47.camel@jlt3.sipsolutions.net>
Johannes Berg wrote:
> On Tue, 2012-06-26 at 14:37 +0200, Michal Kazior wrote:
>> Hi,
>>
>> Here's another respin of channel context patches.
>>
>> Changes:
>>
>> - moved ieee80211_chan_mode
>> - updated chanctx_conf comment
>> - replaced vif_list with refcount
>> - added lockdeps
>> - channel type downgrading support
>> (when a channel context is unassigned from a vif
>> channel type is recalculated for the remaining vifs
>> sharing the same channel context)
>
> Except for that last point which seems to have implementation issues,
> this looks really good too!
>
> How are you planning to proceed from here? I'm happy to pick these up
> even if you're not going to work on using it right away since I think in
> that case I would probably be working on using it pretty soon, but if
> you are planning to work on it that's even better :-)
The next step is to start using channel contexts in mac80211. I was
thinking of using chanctx->channel instead of hw.conf.channel if
.assign_vif_chanctx is defined. I expect some issues like using channel
before it is set.
Hwsim requires .hw_scan and ROC to be implemented to test channel
contexts. hw_scan should be simple (if we skip a few things..) but
haven't looked into the ROC case yet. It also requires some changes to
move channel logic per-vif.
Depending on how things turn out I may start to tackle on mac80211 a bit
more and hw_scan for hwsim. I may send a few patches on monday.
I'll of course resend this patchset today once I fix the pointed out issues.
--
Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2012-06-27 7:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 12:37 [RFC v3] initial channel context implementation Michal Kazior
2012-06-26 12:37 ` [RFC v3 1/7] mac80211: introduce channel context skeleton code Michal Kazior
2012-06-26 12:37 ` [RFC v3 2/7] mac80211: introduce new ieee80211_ops Michal Kazior
2012-06-26 12:37 ` [RFC v3 3/7] mac80211: add drv_* wrappers for channel contexts Michal Kazior
2012-06-26 12:37 ` [RFC v3 4/7] mac80211: add chanctx tracing Michal Kazior
2012-06-26 12:37 ` [RFC v3 5/7] mac80211: use channel context notifications Michal Kazior
2012-06-26 13:35 ` Johannes Berg
2012-06-26 14:01 ` Michal Kazior
2012-06-26 15:34 ` Johannes Berg
2012-06-26 12:37 ` [RFC v3 6/7] mac80211: refactor set_channel_type Michal Kazior
2012-06-26 14:04 ` Eliad Peller
2012-06-26 12:37 ` [RFC v3 7/7] mac80211: reuse channels for channel contexts Michal Kazior
2012-06-26 13:41 ` Johannes Berg
2012-06-26 13:55 ` Michal Kazior
2012-06-26 15:34 ` Johannes Berg
2012-06-26 13:43 ` [RFC v3] initial channel context implementation Johannes Berg
2012-06-27 7:30 ` Michal Kazior [this message]
2012-06-27 8:10 ` Johannes Berg
2012-06-27 10:13 ` Michal Kazior
2012-06-27 11:10 ` Johannes Berg
2012-06-27 12:43 ` Michal Kazior
2012-06-27 14:02 ` Johannes Berg
2012-06-28 6:04 ` Michal Kazior
2012-06-28 7:31 ` Johannes Berg
2012-06-28 7:54 ` Michal Kazior
2012-06-28 8:13 ` Johannes Berg
2012-06-28 9:20 ` Michal Kazior
2012-06-28 9:27 ` Johannes Berg
2012-06-28 9:47 ` Michal Kazior
2012-06-28 7:01 ` Michal Kazior
2012-06-28 8:15 ` Johannes Berg
2012-06-28 8:54 ` Michal Kazior
2012-06-28 9:27 ` Johannes Berg
2012-07-25 10:22 ` 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=4FEAB698.5070309@tieto.com \
--to=michal.kazior@tieto.com \
--cc=johannes@sipsolutions.net \
--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).