On Tue, 2012-11-20 at 17:15 +0200, Victor Goldenshtein wrote:
> > 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.
> >
>
> I thought the same, but to prohibit other channel contexts from being
> added as long as we on DFS channel (not just until the end of the CAC).
Yes, that's a good plan, however, you're missing the fact that you need
to define "as long as we['re] on [the] DFS channel". You forgot that
this isn't a well-defined sentence with channel contexts. As soon as the
CAC operation stops, there's no way to know that we're still on the same
channel, nor do we know if we event *want to*.
So it seems you need different operations:
1) start CAC (as today)
2) event - CAC complete - but don't relinquish channel lock here!
3a) abort CAC - relinquish channel lock, in case userspace no longer
cares
3b) start AP - which moves the channel from being CAC owned to AP owned
Note that you'd also implicitly have to call the CAC abort case (3a) in
case userspace crashes inbetween, so the netlink socket has to own this
similar to the management frame RX handling etc.
> > 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.
> >
>
> What would be "unsafe" here if from the beginning we will allow only one
> channel context ?
Well it seems I was a step ahead of you, I was thinking of the gap
between "CAC ended" and "start AP", see above.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
