From: Michal Kazior <michal.kazior@tieto.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Victor Goldenshtein <victorg@ti.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 6/6] mac80211: add ap channel switch command/event
Date: Wed, 14 Nov 2012 13:19:06 +0100 [thread overview]
Message-ID: <50A38C3A.20908@tieto.com> (raw)
In-Reply-To: <1352892233.9510.26.camel@jlt4.sipsolutions.net>
On 14/11/12 12:23, Johannes Berg wrote:
> On Tue, 2012-11-13 at 17:04 +0200, Victor Goldenshtein wrote:
>
>>> No ... channel contexts are in the kernel now, so you do have to think
>>> about it now.
>>
>> Well thinking is one thing implementing is another ;)
>
> Well ... :)
>
>> This whole DFS implementation initially intended for a single channel
>> mac. I don't might to deal with the channel context stuff but not sure
>> how much available time I"ll have for it, so it might take awhile.
>> I know there are people waiting for this, so I'm thinking would you
>> consider to go first with this single channel DFS support and later to
>> extend it to work with channel context stuff ?
>
> Fair enough, but like I've been telling you, the current code doesn't
> even match the current APIs.
>
> Initially, I thought that for radar detection, you need to reserve the
> channel context (in mac80211), make sure it's the only channel context
> and prohibit other channel contexts from being added, until radar
> detection is done.
>
> However, then I realised that that still doesn't work -- once initial
> radar detection is done, it needs to continue while the AP is active. If
> the channel context was going to be relinquished, or even just the
> channel changed for a few seconds, it would be unsafe. So as a result,
> the radar detect operation has to somehow be coupled to the start AP
> operation and prohibit channel changes and additional channel contexts
> during the entire operation time.
Hmm.. cfg80211 doesn't really know about channel contexts.
The problem I see is that cfg80211 may be in a combination with
`num_different_channels = 1` and mac80211 can have 2 channel contexts
due to channel type incompatibilities.
We'd need to tell cfg80211 that multi-interface is not possible when DFS
is active if we want to at least consider single-channel only DFS.
-- Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2012-11-14 12:19 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
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 [this message]
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=50A38C3A.20908@tieto.com \
--to=michal.kazior@tieto.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=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=victorg@ti.com \
--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 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.