On Fri, 2014-05-23 at 14:23 +0200, Michal Kazior wrote: > Actually I think I've just spotted a little problem. This is also > related to the `[PATCH v6 6/6] cfg80211: remove channel_switch > combination check` thread. > > Currently mac80211 verifies interface combinations in channel_switch. > It has an implicit assumption that channel switch does not change the > number of different channels (or at least it doesn't decrease it). > > We were discussing degradation of number of different channels > earlier, e.g. due to non-radar -> radar change (going from max 2 > channels to 1). With how things are now it's impossible to perform > such a channel switch. Good point. > Basically if we want to support this kind of channel switch we must > remove interface combination checks from ieee80211_channel_switch > because it's simply impossible to know the future (userspace may or > may not submit subsequent requests to match an existing interface > combination). I guess this is a side effect of not having all the channel switches in the API in a single call, which I think you had originally? :-) > So while I still intend to rework the multi-vif reservation a little > (to support cross-swapping at least) I'd like to know if I should > invest my time implementing degradation of number of channels in > multi-vif reservation or not. It doesn't matter to me. If you don't need the feature now, don't implement it now. It's not like it restricts the API (much) making future implementation difficult. 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
