From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([144.76.43.152]:50152 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755370AbaEGMyE (ORCPT ); Wed, 7 May 2014 08:54:04 -0400 Message-ID: <1399467225.10517.35.camel@jlt4.sipsolutions.net> (sfid-20140507_145407_995204_91A0FC6F) Subject: Re: [PATCH v5] mac80211: implement multi-vif in-place reservations From: Johannes Berg To: Michal Kazior Cc: Luca Coelho , linux-wireless , Simon Wunderlich Date: Wed, 07 May 2014 14:53:45 +0200 In-Reply-To: (sfid-20140507_144454_777653_9C1F384B) References: <1397050174-26121-14-git-send-email-michal.kazior@tieto.com> <1398849681-3606-1-git-send-email-michal.kazior@tieto.com> <1399372915.4218.17.camel@jlt4.sipsolutions.net> <1399385141.4218.37.camel@jlt4.sipsolutions.net> <1399450061.5038.10.camel@jlt4.sipsolutions.net> <1399455657.6800.4.camel@dubbel> <1399457760.6800.7.camel@dubbel> <1399460964.10517.12.camel@jlt4.sipsolutions.net> <1399463646.10517.28.camel@jlt4.sipsolutions.net> <1399464536.6800.11.camel@dubbel> <1399464789.10517.29.camel@jlt4.sipsolutions.net> <1399465244.6800.13.camel@dubbel> <1399466312.10517.34.camel@jlt4.sipsolutions.net> (sfid-20140507_144454_777653_9C1F384B) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2014-05-07 at 14:44 +0200, Michal Kazior wrote: > > Ultimately, what I'm trying to say is that instead of the proposed > > switch_vif_chanctx(), we need to have this: > > > > enum ieee80211_chanctx_switch_mode - as before > > > > (*switch_vif_chanctx)(struct ieee80211_hw *hw, > > struct ieee80211_vif **vifs, int n_vifs, > > struct ieee80211_chanctx_conf *old_ctx, > > struct ieee80211_chanctx_conf *new_ctx, > > enum ieee80211_chanctx_switch_mode mode); > > Yeah. This is another way to do it. It does solve the edge case when > you're maxing out on different channels. I thought this was what you were proposing :) > It doesn't, however, (if you don't do transactions) prevent from > chanctx overcommit (i.e. you still can end up with more, albeit > "idle", chanctx allocations in driver). That I don't understand again - what do you mean by "chanctx allocations"? johannes