All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: Jouni Malinen <j@w1.fi>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/3] nl80211: Add probe response offload attribute
Date: Tue, 08 Nov 2011 16:58:48 +0100	[thread overview]
Message-ID: <1320767928.24797.14.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CA+XVXfcrbfVvs+PQCjyrW_QZSKZiAzKUvrqbjqJr47dU73=n2A@mail.gmail.com> (sfid-20111108_165440_062522_2707F77D)

On Tue, 2011-11-08 at 17:53 +0200, Arik Nemtsov wrote:
> On Tue, Nov 8, 2011 at 17:31, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Tue, 2011-11-08 at 16:35 +0200, Arik Nemtsov wrote:
> >> Notify user-space about probe-response offloading support in the driver.
> >>
> >> A wiphy flag is used to indicate support and a bitmap of protocols
> >> determines which protocols are supported.
> >
> >> + * @NL80211_ATTR_PROBE_RESP_OFFLOAD_SUPPORT: Indicates support for probe
> >> + *   response offloading by the driver/firmware.
> >> + *   In addition this attribute holds a bitmap of the supported protocols
> >> + *   for offloading using &enum nl80211_probe_resp_offload_support_attr.
> >
> > I wonder if this should make it more clear that probe requests will be
> > replied to, and this is not optional?
> 
> Actually wl12xx "supports" the legacy way as well. We can operate
> without wpa_s explicitly setting the probe-resp (even though we just
> piece it together in other ways).
> In this sense, it's not a mandatory feature. If wpa_s fails to
> generate it for some reason, we don't want it to fail the AP load. The
> AP will operate just fine.

It'll operate, not sure about "just fine" :-) The way I see it that's
mostly a backward compatibility feature, no?

> >> +++ b/include/net/cfg80211.h
> >> @@ -1693,6 +1693,7 @@ enum wiphy_flags {
> >>       WIPHY_FLAG_AP_UAPSD                     = BIT(14),
> >>       WIPHY_FLAG_SUPPORTS_TDLS                = BIT(15),
> >>       WIPHY_FLAG_TDLS_EXTERNAL_SETUP          = BIT(16),
> >> +     WIPHY_FLAG_SUPPORT_PROBE_RESP_OFFLOAD   = BIT(17),
> >
> > Ditto here, maybe WIPHY_FLAG_HAS_PROBE_RESP_OFFLOAD?
> >
> > As we discussed, ath6kl & similar full-mac drivers with AP SME in the
> > device should set this to advertise the probe protocol feature set they
> > support (by passing up), and even for wl12xx it's not optional.
> 
> All this has to do with user-space semantics. Currently hostap always
> sets the probe-resp IEs, without checking offloading support.

Which is fine too, but I think ath6kl should set this value right?

johannes


  reply	other threads:[~2011-11-08 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 14:35 [PATCH v3 1/3] nl80211: Add probe response offload attribute Arik Nemtsov
2011-11-08 14:35 ` [PATCH v3 2/3] nl80211: Pass probe response data to drivers Arik Nemtsov
2011-11-08 15:32   ` Johannes Berg
2011-11-08 16:04     ` Arik Nemtsov
2011-11-08 16:10       ` Johannes Berg
2011-11-08 14:35 ` [PATCH v3 3/3] mac80211: Save probe response data for bss Arik Nemtsov
2011-11-08 15:34   ` Johannes Berg
2011-11-08 16:07     ` Arik Nemtsov
2011-11-08 15:31 ` [PATCH v3 1/3] nl80211: Add probe response offload attribute Johannes Berg
2011-11-08 15:53   ` Arik Nemtsov
2011-11-08 15:58     ` Johannes Berg [this message]
2011-11-08 16:17       ` Arik Nemtsov

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=1320767928.24797.14.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arik@wizery.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    /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.