From: Luciano Coelho <luciano.coelho@intel.com>
To: Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Michal Kazior <michal.kazior@tieto.com>,
sw@simonwunderlich.de, andrei.otcheretianski@intel.com
Subject: Re: [PATCH v6 3/3] mac80211: allow reservation of a running chanctx
Date: Mon, 10 Mar 2014 09:37:20 +0200 [thread overview]
Message-ID: <1394437040.18265.1.camel@dubbel> (raw)
In-Reply-To: <CAB3XZEe+-sdGfMupP7x0fKHCfevCtZDY7UrF6rRyL3==pnZf5Q@mail.gmail.com>
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.
next prev parent reply other threads:[~2014-03-10 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 14:40 [PATCH v6 0/3] mac802111: channel context reservation Luciano Coelho
2014-03-09 14:40 ` [PATCH v6 1/3] mac80211: split ieee80211_vif_change_channel in two Luciano Coelho
2014-03-09 14:40 ` [PATCH v6 2/3] mac80211: implement chanctx reservation Luciano Coelho
2014-03-09 15:08 ` Eliad Peller
2014-03-10 7:43 ` Luciano Coelho
2014-03-09 14:40 ` [PATCH v6 3/3] mac80211: allow reservation of a running chanctx Luciano Coelho
2014-03-09 15:13 ` Eliad Peller
2014-03-10 7:37 ` Luciano Coelho [this message]
2014-03-10 8:32 ` Eliad Peller
2014-03-10 9:03 ` Michal Kazior
2014-03-10 9:15 ` Luca Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1394437040.18265.1.camel@dubbel \
--to=luciano.coelho@intel.com \
--cc=andrei.otcheretianski@intel.com \
--cc=eliad@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=sw@simonwunderlich.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).