On 13 May 2014 15:42, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2014-05-08 at 12:41 +0200, Michal Kazior wrote: > >> Then, if you want to avoid the chanctx overcommit problem, you need to >> make switch_vif_chanctx() to act as drv_add_chanctx(old_ctx) and >> drv_remove_chanctx(new_ctx) implicitly, i.e. >> >> drv_switch_vif_chanctx(hw, vifs, n_vifs, old_ctx, new_ctx, SWAP); >> >> instead of: >> >> drv_add_chanctx(new_ctx); >> drv_switch_vif_chanctx(hw, vifs, n_vifs, old_ctx, new_ctx, SWAP); >> drv_remove_chanctx(old_ctx); > > That's pretty much what I'd considered, except that now as far as I read > the thread this wasn't sufficient for multi-context, so we'd need lists > of old/new contexts? Hmm.. In what cases do you need a list of old/new contexts? Michal -- 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
