linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victor Goldenshtein <victorg@ti.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kgiori@qca.qualcomm.com" <kgiori@qca.qualcomm.com>,
	"mcgrof@frijolero.org" <mcgrof@frijolero.org>,
	"zefir.kurtisi@neratec.com" <zefir.kurtisi@neratec.com>,
	"adrian.chadd@gmail.com" <adrian.chadd@gmail.com>,
	"j@w1.fi" <j@w1.fi>, "coelho@ti.com" <coelho@ti.com>,
	"igalc@ti.com" <igalc@ti.com>,
	"adrian@freebsd.org" <adrian@freebsd.org>,
	"nbd@nbd.name" <nbd@nbd.name>,
	"simon.wunderlich@s2003.tu-chemnitz.de"
	<simon.wunderlich@s2003.tu-chemnitz.de>
Subject: Re: [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command
Date: Tue, 13 Nov 2012 17:04:09 +0200	[thread overview]
Message-ID: <50A26169.9060602@ti.com> (raw)
In-Reply-To: <1352129348.9466.23.camel@jlt4.sipsolutions.net>

On 05/11/2012 17:29, Johannes Berg wrote:
> On Thu, 2012-11-01 at 09:54 +0200, Victor Goldenshtein wrote:
>
>>> This however introduces a new problem. Let's suppose we have 2 APs on
>>> channel 1. The device doesn't support multi-channel. We won't be able to
>>> switch channel on these APs at all.
>>>
>>> We might want to change the channel switch to resolve around the channel
>>> itself (not the interface) - so we'd be saying "move all interfaces with
>>> channel X to channel Y" instead of "move interface X to channel Y".
>>>
>>> Or we could let the driver decide what it'll do - e.g. silently switch
>>> more than one interface to a different channel (which makes sense with
>>> AP/DFS I guess) and just notify cfg/userspace about it. That would
>>> require us to provide a way to switch interfaces (atomically possibly)
>>> between channels while keeping in sync with interface combinations though.
>>>
>>
>> If the driver/device supports MR only on a SC - means it doesn't
>
> What's MR? SC = single channel?
>

MR - Multi-Role, SC - Single Channel.

>> supports channel switch in MR, so basically the radar detection event
>> triggers AP channel switch which fails (with this new check) and the AP
>> shut down.
>
> But I was speaking of two interfaces on a single channel.
>

the radar detection is per channel and for this case we have the 
"if·(chan->cac_started)" check, see 6/6.

>> Of course there are possible driver specific workarounds (as you
>> mentioned above) but these are not part of this series.
>
> yeah but you should probably allow for some strategy of handling this?
>

If we talking about the case of running two APs on the same channel on a 
single channel platform then the strategy should be (at least at first 
stage) to shut down both APs after radar detection event.

Later we can discuss about the idea of "switching interfaces" (switch 
both this APs to a new channel).


-- 
Thanks,
Victor.

  reply	other threads:[~2012-11-13 15:05 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14 14:48 [PATCH v4 0/6] nl/cfg/mac80211: add DFS master ability Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 1/6] nl80211/cfg80211: add radar detection command/event Victor Goldenshtein
2012-10-16 19:01   ` Johannes Berg
2012-10-17 16:20     ` Zefir Kurtisi
2012-10-17 16:23       ` Johannes Berg
2012-10-21 16:40     ` Victor Goldenshtein
2012-10-22 12:55       ` Johannes Berg
2012-11-01  7:54         ` Victor Goldenshtein
2012-11-05 15:21           ` Johannes Berg
2012-11-13 15:04             ` Victor Goldenshtein
2012-11-13 18:05               ` Simon Wunderlich
2012-11-20 15:14                 ` Victor Goldenshtein
2012-11-26 10:52                   ` Johannes Berg
2012-11-14 11:19               ` Johannes Berg
2012-11-20 15:15                 ` Victor Goldenshtein
2012-11-14 12:32             ` Michal Kazior
2012-11-14 12:38               ` Johannes Berg
2012-11-20 15:15                 ` Victor Goldenshtein
2012-11-26 10:51                   ` Johannes Berg
2012-10-14 14:48 ` [PATCH v4 2/6] mac80211: " Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 3/6] nl80211/cfg80211: add ability to enable TX on op-channel Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 4/6] mac80211: " Victor Goldenshtein
2012-10-16 19:03   ` Johannes Berg
2012-10-21 16:40     ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command Victor Goldenshtein
2012-10-16 19:06   ` Johannes Berg
2012-10-21 16:40     ` Victor Goldenshtein
2012-10-22 12:52       ` Johannes Berg
2012-11-01  7:54         ` Victor Goldenshtein
2012-11-05 15:27           ` Johannes Berg
2012-11-13 15:04             ` Victor Goldenshtein
2012-10-23  6:20   ` Michal Kazior
2012-11-01  7:54     ` Victor Goldenshtein
2012-11-01 17:15       ` Adrian Chadd
2012-11-01 19:32         ` Johannes Berg
2012-11-05 15:29       ` Johannes Berg
2012-11-13 15:04         ` Victor Goldenshtein [this message]
2012-10-14 14:48 ` [PATCH v4 6/6] mac80211: add ap channel switch command/event Victor Goldenshtein
2012-10-16 19:07   ` Johannes Berg
2012-10-21 16:40     ` Victor Goldenshtein
2012-10-22 12:56       ` Johannes Berg
2012-11-01  7:54         ` Victor Goldenshtein
2012-11-05 15:23           ` Johannes Berg
2012-11-13 15:04             ` Victor Goldenshtein
2012-11-14 11:23               ` Johannes Berg
2012-11-14 12:19                 ` Michal Kazior
2012-11-14 12:38                   ` Johannes Berg
2012-11-20 15:15                     ` Victor Goldenshtein
2012-11-26 10:50                       ` Johannes Berg
2012-11-20 15:15                 ` Victor Goldenshtein
2012-11-26 10:50                   ` 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=50A26169.9060602@ti.com \
    --to=victorg@ti.com \
    --cc=adrian.chadd@gmail.com \
    --cc=adrian@freebsd.org \
    --cc=coelho@ti.com \
    --cc=igalc@ti.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=kgiori@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@frijolero.org \
    --cc=michal.kazior@tieto.com \
    --cc=nbd@nbd.name \
    --cc=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=zefir.kurtisi@neratec.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).