On Wed, 2014-05-07 at 14:20 +0200, Michal Kazior wrote: > > 1) for_each_vif: switch vif from oldctx to newctx > > 2) add newctx > > for_each_vif: switch vif from oldctx to newctx > > del oldctx > > > > With the option between 1/2 being selected by the flags. I don't see > > what the driver has to infer about it being a channel switch - it > > necessarily is one, no? > > Yeah - existing usecases include only CSA and some primitive ops. > > What I mean is if you want to avoid chanctx overcommit you need to > perform (2) the other way around (i.e. first unassign and delete > oldctx and then create newctx), at least internally. This would simply > be more of a hassle with multiple call transaction API. Well, sure you really have to do it the other way around - but we'd be assuming the driver does whatever it can internally, for that call 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
