diff mbox

[v6,3/3] mac80211: allow reservation of a running chanctx

Message ID 1394376039-9644-4-git-send-email-luciano.coelho@intel.com (mailing list archive)
State Not Applicable, archived
Headers show

Commit Message

Luca Coelho March 9, 2014, 2:40 p.m. UTC
With single-channel drivers, we need to be able to change a running
chanctx if we want to use chanctx reservation.  Not all drivers may be
able to do this, so add a flag that indicates support for it.

Changing a running chanctx can also be used as an optimization in
multi-channel drivers when the context needs to be reserved for future
usage.

Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
reserved so nobody else can use it (since we know it's going to
change).  In the future, we may allow several vifs to use the same
reservation as long as they plan to use the chanctx on the same
future channel.

Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
---
In v3:

   * reworded the TODO, slightly;

In v4:

   * remove IEEE80211_CHANCTX_RESERVED and the reserved_mode element;
   * increase refcount also for "in-place" changes;
   * stop queues also before doing an "in-place" change;
   * refactor ieee80211_use_reserved_chanctx() a bit to fit "in-place"
     better;

In v5:

   * fix checkpatch warnings;

In v6:

   * return ret in ieee80211_chanctx_is_reserved();
   * check if sdata is running in ieee80211_chanctx_is_reserved();
   * keep check for IEEE80211_CHANCTX_EXCLUSIVE in
     ieee80211_find_channel();
   * use break instead of goto out in ieee80211_chanctx_is_reserved();
---
 include/net/mac80211.h |  7 ++++
 net/mac80211/chan.c    | 97 ++++++++++++++++++++++++++++++++++++--------------
 2 files changed, 77 insertions(+), 27 deletions(-)

Comments

Eliad Peller March 9, 2014, 3:13 p.m. UTC | #1
On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@intel.com> wrote:
> With single-channel drivers, we need to be able to change a running
> chanctx if we want to use chanctx reservation.  Not all drivers may be
> able to do this, so add a flag that indicates support for it.
>
> Changing a running chanctx can also be used as an optimization in
> multi-channel drivers when the context needs to be reserved for future
> usage.
>
> Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
> reserved so nobody else can use it (since we know it's going to
> change).  In the future, we may allow several vifs to use the same
> reservation as long as they plan to use the chanctx on the same
> future channel.
>
> Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
> ---
[...]

> @@ -177,7 +198,12 @@ ieee80211_find_chanctx(struct ieee80211_local *local,
>         list_for_each_entry(ctx, &local->chanctx_list, list) {
>                 const struct cfg80211_chan_def *compat;
>
> -               if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
> +               /* We don't support chanctx reservation for multiple
> +                * vifs yet, so don't allow reserved chanctxs to be
> +                * reused.
> +                */
> +               if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
> +                   ieee80211_chanctx_is_reserved(local, ctx))
>                         continue;
>
i'm not sure that's correct.
you might want to find a chanctx in order to use it, not only for
reservation. any reason to reject it in this case?

Eliad.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Luca Coelho March 10, 2014, 7:37 a.m. UTC | #2
On Sun, 2014-03-09 at 17:13 +0200, Eliad Peller wrote:
> On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@intel.com> wrote:
> > With single-channel drivers, we need to be able to change a running
> > chanctx if we want to use chanctx reservation.  Not all drivers may be
> > able to do this, so add a flag that indicates support for it.
> >
> > Changing a running chanctx can also be used as an optimization in
> > multi-channel drivers when the context needs to be reserved for future
> > usage.
> >
> > Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
> > reserved so nobody else can use it (since we know it's going to
> > change).  In the future, we may allow several vifs to use the same
> > reservation as long as they plan to use the chanctx on the same
> > future channel.
> >
> > Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
> > ---
> [...]
> 
> > @@ -177,7 +198,12 @@ ieee80211_find_chanctx(struct ieee80211_local *local,
> >         list_for_each_entry(ctx, &local->chanctx_list, list) {
> >                 const struct cfg80211_chan_def *compat;
> >
> > -               if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
> > +               /* We don't support chanctx reservation for multiple
> > +                * vifs yet, so don't allow reserved chanctxs to be
> > +                * reused.
> > +                */
> > +               if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
> > +                   ieee80211_chanctx_is_reserved(local, ctx))
> >                         continue;
> >
> i'm not sure that's correct.
> you might want to find a chanctx in order to use it, not only for
> reservation. any reason to reject it in this case?

At the moment we don't support multi-vifs switching at the same time, so
we don't allow anyone else to use a chanctx while it's reserved.

--
Luca.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Eliad Peller March 10, 2014, 8:32 a.m. UTC | #3
On Mon, Mar 10, 2014 at 9:37 AM, Luciano Coelho
<luciano.coelho@intel.com> wrote:
> On Sun, 2014-03-09 at 17:13 +0200, Eliad Peller wrote:
>> On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@intel.com> wrote:
>> > With single-channel drivers, we need to be able to change a running
>> > chanctx if we want to use chanctx reservation.  Not all drivers may be
>> > able to do this, so add a flag that indicates support for it.
>> >
>> > Changing a running chanctx can also be used as an optimization in
>> > multi-channel drivers when the context needs to be reserved for future
>> > usage.
>> >
>> > Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
>> > reserved so nobody else can use it (since we know it's going to
>> > change).  In the future, we may allow several vifs to use the same
>> > reservation as long as they plan to use the chanctx on the same
>> > future channel.
>> >
>> > Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
>> > ---
>> [...]
>>
>> > @@ -177,7 +198,12 @@ ieee80211_find_chanctx(struct ieee80211_local *local,
>> >         list_for_each_entry(ctx, &local->chanctx_list, list) {
>> >                 const struct cfg80211_chan_def *compat;
>> >
>> > -               if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
>> > +               /* We don't support chanctx reservation for multiple
>> > +                * vifs yet, so don't allow reserved chanctxs to be
>> > +                * reused.
>> > +                */
>> > +               if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
>> > +                   ieee80211_chanctx_is_reserved(local, ctx))
>> >                         continue;
>> >
>> i'm not sure that's correct.
>> you might want to find a chanctx in order to use it, not only for
>> reservation. any reason to reject it in this case?
>
> At the moment we don't support multi-vifs switching at the same time, so
> we don't allow anyone else to use a chanctx while it's reserved.
>
i'm not talking about multi-vifs switching.
consider the following scenario:
sta connected on channel 40
ap beaconing on channel 60

now, you want (for whatever reason) to switch the ap to channel 40.
you'll reserve the sta's chanctx, and increase its refcount (to 2).

now a new sta vif is added, and tries to connect on channel 40.
the check above will skip the existing channel context (because it's
also reserved) although there is no reason it won't be used.

Eliad.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Michal Kazior March 10, 2014, 9:03 a.m. UTC | #4
On 10 March 2014 09:32, Eliad Peller <eliad@wizery.com> wrote:
> On Mon, Mar 10, 2014 at 9:37 AM, Luciano Coelho
> <luciano.coelho@intel.com> wrote:
>> On Sun, 2014-03-09 at 17:13 +0200, Eliad Peller wrote:
>>> On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@intel.com> wrote:
>>> > With single-channel drivers, we need to be able to change a running
>>> > chanctx if we want to use chanctx reservation.  Not all drivers may be
>>> > able to do this, so add a flag that indicates support for it.
>>> >
>>> > Changing a running chanctx can also be used as an optimization in
>>> > multi-channel drivers when the context needs to be reserved for future
>>> > usage.
>>> >
>>> > Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
>>> > reserved so nobody else can use it (since we know it's going to
>>> > change).  In the future, we may allow several vifs to use the same
>>> > reservation as long as they plan to use the chanctx on the same
>>> > future channel.
>>> >
>>> > Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
>>> > ---
>>> [...]
>>>
>>> > @@ -177,7 +198,12 @@ ieee80211_find_chanctx(struct ieee80211_local *local,
>>> >         list_for_each_entry(ctx, &local->chanctx_list, list) {
>>> >                 const struct cfg80211_chan_def *compat;
>>> >
>>> > -               if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
>>> > +               /* We don't support chanctx reservation for multiple
>>> > +                * vifs yet, so don't allow reserved chanctxs to be
>>> > +                * reused.
>>> > +                */
>>> > +               if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
>>> > +                   ieee80211_chanctx_is_reserved(local, ctx))
>>> >                         continue;
>>> >
>>> i'm not sure that's correct.
>>> you might want to find a chanctx in order to use it, not only for
>>> reservation. any reason to reject it in this case?
>>
>> At the moment we don't support multi-vifs switching at the same time, so
>> we don't allow anyone else to use a chanctx while it's reserved.
>>
> i'm not talking about multi-vifs switching.
> consider the following scenario:
> sta connected on channel 40
> ap beaconing on channel 60
>
> now, you want (for whatever reason) to switch the ap to channel 40.
> you'll reserve the sta's chanctx, and increase its refcount (to 2).
>
> now a new sta vif is added, and tries to connect on channel 40.
> the check above will skip the existing channel context (because it's
> also reserved) although there is no reason it won't be used.

Good point. I have this case covered in my multi-vif csa patches. We
could transplant it into Luca's patch?


Micha?
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Luca Coelho March 10, 2014, 9:15 a.m. UTC | #5
On Mon, 2014-03-10 at 10:03 +0100, Michal Kazior wrote:
> On 10 March 2014 09:32, Eliad Peller <eliad@wizery.com> wrote:
> > On Mon, Mar 10, 2014 at 9:37 AM, Luciano Coelho
> > <luciano.coelho@intel.com> wrote:
> >> On Sun, 2014-03-09 at 17:13 +0200, Eliad Peller wrote:
> >>> On Sun, Mar 9, 2014 at 4:40 PM, Luciano Coelho <luciano.coelho@intel.com> wrote:
> >>> > With single-channel drivers, we need to be able to change a running
> >>> > chanctx if we want to use chanctx reservation.  Not all drivers may be
> >>> > able to do this, so add a flag that indicates support for it.
> >>> >
> >>> > Changing a running chanctx can also be used as an optimization in
> >>> > multi-channel drivers when the context needs to be reserved for future
> >>> > usage.
> >>> >
> >>> > Introduce IEEE80211_CHANCTX_RESERVED chanctx mode to mark a channel as
> >>> > reserved so nobody else can use it (since we know it's going to
> >>> > change).  In the future, we may allow several vifs to use the same
> >>> > reservation as long as they plan to use the chanctx on the same
> >>> > future channel.
> >>> >
> >>> > Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
> >>> > ---
> >>> [...]
> >>>
> >>> > @@ -177,7 +198,12 @@ ieee80211_find_chanctx(struct ieee80211_local *local,
> >>> >         list_for_each_entry(ctx, &local->chanctx_list, list) {
> >>> >                 const struct cfg80211_chan_def *compat;
> >>> >
> >>> > -               if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
> >>> > +               /* We don't support chanctx reservation for multiple
> >>> > +                * vifs yet, so don't allow reserved chanctxs to be
> >>> > +                * reused.
> >>> > +                */
> >>> > +               if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
> >>> > +                   ieee80211_chanctx_is_reserved(local, ctx))
> >>> >                         continue;
> >>> >
> >>> i'm not sure that's correct.
> >>> you might want to find a chanctx in order to use it, not only for
> >>> reservation. any reason to reject it in this case?
> >>
> >> At the moment we don't support multi-vifs switching at the same time, so
> >> we don't allow anyone else to use a chanctx while it's reserved.
> >>
> > i'm not talking about multi-vifs switching.
> > consider the following scenario:
> > sta connected on channel 40
> > ap beaconing on channel 60
> >
> > now, you want (for whatever reason) to switch the ap to channel 40.
> > you'll reserve the sta's chanctx, and increase its refcount (to 2).
> >
> > now a new sta vif is added, and tries to connect on channel 40.
> > the check above will skip the existing channel context (because it's
> > also reserved) although there is no reason it won't be used.
> 
> Good point. I have this case covered in my multi-vif csa patches. We
> could transplant it into Luca's patch?

Yes, it's a good point.  What would happen with this patch is that the
new STA will get a new chanctx, so in theory it would still work (though
wasting resources. as it could be).

If your fix is simple, we could transplant it here.  But if it's more
complex, I think we could have it as a new patch on top of my series.
Nobody is using channel reservation yet, so I don't think that would be
a big problem.

--
Luca.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 86faa41..b35c608 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -1553,6 +1553,12 @@  struct ieee80211_tx_control {
  *	for a single active channel while using channel contexts. When support
  *	is not enabled the default action is to disconnect when getting the
  *	CSA frame.
+ *
+ * @IEEE80211_HW_CHANGE_RUNNING_CHANCTX: The hardware can change a
+ *	channel context on-the-fly.  This is needed for channel switch
+ *	on single-channel hardware.  It can also be used as an
+ *	optimization in certain channel switch cases with
+ *	multi-channel.
  */
 enum ieee80211_hw_flags {
 	IEEE80211_HW_HAS_RATE_CONTROL			= 1<<0,
@@ -1584,6 +1590,7 @@  enum ieee80211_hw_flags {
 	IEEE80211_HW_TIMING_BEACON_ONLY			= 1<<26,
 	IEEE80211_HW_SUPPORTS_HT_CCK_RATES		= 1<<27,
 	IEEE80211_HW_CHANCTX_STA_CSA			= 1<<28,
+	IEEE80211_HW_CHANGE_RUNNING_CHANCTX		= 1<<29,
 };
 
 /**
diff --git a/net/mac80211/chan.c b/net/mac80211/chan.c
index 2acf973..a6fdc14 100644
--- a/net/mac80211/chan.c
+++ b/net/mac80211/chan.c
@@ -162,6 +162,27 @@  static void ieee80211_change_chanctx(struct ieee80211_local *local,
 	}
 }
 
+static bool ieee80211_chanctx_is_reserved(struct ieee80211_local *local,
+				     struct ieee80211_chanctx *ctx)
+{
+	struct ieee80211_sub_if_data *sdata;
+	bool ret = false;
+
+	lockdep_assert_held(&local->chanctx_mtx);
+	rcu_read_lock();
+	list_for_each_entry_rcu(sdata, &local->interfaces, list) {
+		if (!ieee80211_sdata_running(sdata))
+			continue;
+		if (sdata->reserved_chanctx == ctx) {
+			ret = true;
+			break;
+		}
+	}
+
+	rcu_read_unlock();
+	return ret;
+}
+
 static struct ieee80211_chanctx *
 ieee80211_find_chanctx(struct ieee80211_local *local,
 		       const struct cfg80211_chan_def *chandef,
@@ -177,7 +198,12 @@  ieee80211_find_chanctx(struct ieee80211_local *local,
 	list_for_each_entry(ctx, &local->chanctx_list, list) {
 		const struct cfg80211_chan_def *compat;
 
-		if (ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE)
+		/* We don't support chanctx reservation for multiple
+		 * vifs yet, so don't allow reserved chanctxs to be
+		 * reused.
+		 */
+		if ((ctx->mode == IEEE80211_CHANCTX_EXCLUSIVE) ||
+		    ieee80211_chanctx_is_reserved(local, ctx))
 			continue;
 
 		compat = cfg80211_chandef_compatible(&ctx->conf.def, chandef);
@@ -652,11 +678,20 @@  int ieee80211_vif_reserve_chanctx(struct ieee80211_sub_if_data *sdata,
 	/* try to find another context with the chandef we want */
 	new_ctx = ieee80211_find_chanctx(local, chandef, mode);
 	if (!new_ctx) {
-		/* create a new context */
-		new_ctx = ieee80211_new_chanctx(local, chandef, mode);
-		if (IS_ERR(new_ctx)) {
-			ret = PTR_ERR(new_ctx);
-			goto out;
+		if (curr_ctx->refcount == 1 &&
+		    (local->hw.flags & IEEE80211_HW_CHANGE_RUNNING_CHANCTX)) {
+			/* if we're the only users of the chanctx and
+			 * the driver supports changing a running
+			 * context, reserve our current context
+			 */
+			new_ctx = curr_ctx;
+		} else {
+			/* create a new context and reserve it */
+			new_ctx = ieee80211_new_chanctx(local, chandef, mode);
+			if (IS_ERR(new_ctx)) {
+				ret = PTR_ERR(new_ctx);
+				goto out;
+			}
 		}
 	}
 
@@ -701,37 +736,45 @@  int ieee80211_vif_use_reserved_context(struct ieee80211_sub_if_data *sdata,
 	ieee80211_stop_queues_by_reason(&local->hw,
 					IEEE80211_MAX_QUEUE_MAP,
 					IEEE80211_QUEUE_STOP_REASON_CHANCTX);
+	/* unref our reservation */
+	ctx->refcount--;
+	sdata->reserved_chanctx = NULL;
 
-	ieee80211_unassign_vif_chanctx(sdata, old_ctx);
-	if (old_ctx->refcount == 0)
-		ieee80211_free_chanctx(local, old_ctx);
+	if (old_ctx == ctx) {
+		/* This is our own context, just change it */
+		ret = __ieee80211_vif_change_channel(sdata, old_ctx,
+						     &local_changed);
+		if (ret)
+			goto out;
+	} else {
+		ieee80211_unassign_vif_chanctx(sdata, old_ctx);
+		if (old_ctx->refcount == 0)
+			ieee80211_free_chanctx(local, old_ctx);
 
-	if (sdata->vif.bss_conf.chandef.width != sdata->reserved_chandef.width)
-		local_changed |= BSS_CHANGED_BANDWIDTH;
+		if (sdata->vif.bss_conf.chandef.width !=
+		    sdata->reserved_chandef.width)
+			local_changed |= BSS_CHANGED_BANDWIDTH;
 
-	sdata->vif.bss_conf.chandef = sdata->reserved_chandef;
+		sdata->vif.bss_conf.chandef = sdata->reserved_chandef;
 
-	/* unref our reservation before assigning */
-	ctx->refcount--;
-	sdata->reserved_chanctx = NULL;
-	ret = ieee80211_assign_vif_chanctx(sdata, ctx);
-	if (ret) {
-		/* if assign fails refcount stays the same */
-		if (ctx->refcount == 0)
-			ieee80211_free_chanctx(local, ctx);
-		goto out_wake;
+		ret = ieee80211_assign_vif_chanctx(sdata, ctx);
+		if (ret) {
+			/* if assign fails refcount stays the same */
+			if (ctx->refcount == 0)
+				ieee80211_free_chanctx(local, ctx);
+			goto out;
+		}
+
+		ieee80211_recalc_chanctx_chantype(local, ctx);
+		ieee80211_recalc_smps_chanctx(local, ctx);
+		ieee80211_recalc_radar_chanctx(local, ctx);
 	}
 
 	*changed = local_changed;
-
-	ieee80211_recalc_chanctx_chantype(local, ctx);
-	ieee80211_recalc_smps_chanctx(local, ctx);
-	ieee80211_recalc_radar_chanctx(local, ctx);
-out_wake:
+out:
 	ieee80211_wake_queues_by_reason(&sdata->local->hw,
 					IEEE80211_MAX_QUEUE_MAP,
 					IEEE80211_QUEUE_STOP_REASON_CHANCTX);
-out:
 	mutex_unlock(&local->chanctx_mtx);
 	return ret;
 }