From: Johannes Berg <johannes@sipsolutions.net>
To: Sam Leffler <sleffler@chromium.org>
Cc: "John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, eliad <eliad@wizery.com>,
coelho <coelho@ti.com>
Subject: Re: [PATCH 0/3] add scan flags support
Date: Thu, 27 Sep 2012 11:13:39 +0200 [thread overview]
Message-ID: <1348737219.10353.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20120926165952.766801E10D3@sleffler.sfo.corp.google.com> (sfid-20120926_185956_215056_52A41944)
On Tue, 2012-09-25 at 15:49 -0700, Sam Leffler wrote:
> These add per-scan request controls for optional behaviours we've found
> useful (they've been in Chrome OS for a long time). A patch for iw will
> follow separately and the mods for wpa_supplicant are in our repo and
> I'll push them to Jouni if these are accepted.
>
> Sam Leffler (3):
> {nl,cfg}80211: add a flags word to scan requests
> mac80211: add support for tx to abort scan requests
> cfg80211: add support for flushing old scan results
I like the flushing one, but I'm not so sure about the TX abort thing.
How do you suggest to handle that when scanning is offloaded to the
driver and/or firmware? Especially given that multi-channel is going to
require a firmware implementation, I'm not sure how to achieve good
behaviour across the different implementations.
Maybe it'd be worthwhile to go for a more generic approach, marking
scans as "low priority" or "high priority" or similar, and then
implementing such behaviour based on such settings? Our device for
example has a notion of "background scan" vs. "forced scan", which
behave differently in the firmware, and it would be useful to be able to
use these different behaviours. However, I can't say that "TX abort"
would be a guaranteed scan behaviour for a "background scan".
johannes
next prev parent reply other threads:[~2012-09-27 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 22:49 [PATCH 0/3] add scan flags support Sam Leffler
2012-09-26 19:44 ` Bing Zhao
2012-09-27 9:13 ` Johannes Berg [this message]
2012-09-27 9:31 ` Eliad Peller
2012-09-27 9:43 ` Arik Nemtsov
2012-09-27 16:43 ` Sam Leffler
2012-09-27 16:39 ` Sam Leffler
2012-09-28 10:57 ` Johannes Berg
2012-09-28 20:27 ` Sam Leffler
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=1348737219.10353.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=coelho@ti.com \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sleffler@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox