From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 9/9] mac80211: implement multi-interface CSA
Date: Thu, 16 Jan 2014 10:31:46 +0100 [thread overview]
Message-ID: <1389864706.4345.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQ=UJNLD3dmzD4PDK1exSJFeWTdpkAHc2YvVbktugw_AyQ@mail.gmail.com> (sfid-20140116_102805_794169_3235EA94)
On Thu, 2014-01-16 at 10:28 +0100, Michal Kazior wrote:
> On 15 January 2014 14:22, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Wed, 2014-01-15 at 13:04 +0100, Michal Kazior wrote:
> >> This implements a fairly simple multi-interface
> >> CSA. It doesn't support multiple channel
> >> contexts so it doesn't support multi-channel.
> >
> > It seems that this also means that somewhere you need to advertise the
> > multi-switch feature. I guess you need that anyway, but this makes it
> > obvious.
>
> I don't really understand. Do we really need it? You want to advertise
> it just to cfg80211 or all the way up to userspace?
It seems it would be needed all the way to userspace so it knows whether
it can expect multi-vif CSA to be available? Or would you just want to
try & fail? Wouldn't that potentially impact channel selection since
you'd want to not pick radar channels for multi-vif? Not really sure ...
Maybe the expectation is that internally there will be no drivers that
don't support it, i.e. if a driver implements the cfg80211 API at all
then it must support multi-vif CSA?
johannes
next prev parent reply other threads:[~2014-01-16 9:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:04 [RFC 0/9] mac80211: multi-interface CSA Michal Kazior
2014-01-15 12:04 ` [RFC 1/9] mac80211: fix possible memory leak on AP CSA failure Michal Kazior
2014-01-15 12:04 ` [RFC 2/9] mac80211: treat IBSS CSA finish failure seriously Michal Kazior
2014-01-15 13:07 ` Luca Coelho
2014-01-15 12:04 ` [RFC 3/9] mac80211: move csa_active setting in STA CSA Michal Kazior
2014-01-15 13:17 ` Johannes Berg
2014-01-15 12:04 ` [RFC 4/9] mac80211: fix sdata->radar_required locking Michal Kazior
2014-01-15 12:04 ` [RFC 5/9] mac80211: improve CSA locking Michal Kazior
2014-01-15 12:04 ` [RFC 6/9] mac80211: track CSA globally Michal Kazior
2014-01-15 13:19 ` Johannes Berg
2014-01-15 13:28 ` Michal Kazior
2014-01-15 13:29 ` Johannes Berg
2014-01-15 14:11 ` Michal Kazior
2014-01-15 14:21 ` Johannes Berg
2014-01-15 12:04 ` [RFC 7/9] Revert "cfg80211: disable CSA for all drivers" Michal Kazior
2014-01-15 12:04 ` [RFC 8/9] ath9k: prepare for multi-interface CSA support Michal Kazior
2014-01-15 12:04 ` [RFC 9/9] mac80211: implement multi-interface CSA Michal Kazior
2014-01-15 13:22 ` Johannes Berg
2014-01-16 9:28 ` Michal Kazior
2014-01-16 9:31 ` Johannes Berg [this message]
2014-01-16 10:33 ` Michal Kazior
2014-01-20 11:06 ` Johannes Berg
2014-01-16 11:04 ` Eliad Peller
2014-01-16 11:41 ` Michal Kazior
2014-01-15 13:21 ` [RFC 0/9] mac80211: " 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=1389864706.4345.1.camel@jlt4.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 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.