From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bing Zhao <bzhao@marvell.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH v2] nl/cfg80211: advertise OBSS scan offload capability
Date: Mon, 12 Nov 2012 13:17:19 +0200 [thread overview]
Message-ID: <20121112111719.GA6079@w1.fi> (raw)
In-Reply-To: <1352712697.9525.4.camel@jlt4.sipsolutions.net>
On Mon, Nov 12, 2012 at 10:31:37AM +0100, Johannes Berg wrote:
> On Fri, 2012-11-09 at 17:51 -0800, Bing Zhao wrote:
> > From: Amitkumar Karwar <akarwar@marvell.com>
> >
> > wpa_supplicant will do OBSS scan for drivers that implement
> > auth/assoc API. Drivers that implement nl80211 connect API
> > (rather than auth/assoc) may need wpa_supplicant to do this
> > as well.
> Applied, but I changed a lot ;-)
>
> Notably, I reworded the constant name to be
> NL80211_FEATURE_NEED_OBSS_SCAN, since we typically use the term
> "offload" to mean that the *device* does something, not to mean that
> *userspace* does something.
Sorry for being a bit late with my comments, but does this single flag
really cover expected use cases? I would assume that number of more full
MAC -like designs will have to move to separate auth/assoc commands
instead of using connect API in the future (e.g., for FT and SAE).
However, those drivers do not necessarily expect user space to take care
of OBSS scans. I understand that this is not currently supported since
wpa_supplicant assuming auth/assoc to mean user space SME, but it should
be kept in mind that that may need to change in the future..
I guess we can handle the auth/assoc without user space OBSS scan
separately (a new feature flag for stopping OBSS scan?), so I'm fine
with this patch moving ahead as-is.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2012-11-12 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 1:51 [PATCH v2] nl/cfg80211: advertise OBSS scan offload capability Bing Zhao
2012-11-12 9:31 ` Johannes Berg
2012-11-12 11:17 ` Jouni Malinen [this message]
2012-11-12 11:42 ` Johannes Berg
2012-11-12 21:38 ` Bing Zhao
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=20121112111719.GA6079@w1.fi \
--to=j@w1.fi \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.