From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Scanning improvements for multiple VIFS.
Date: Sat, 13 Nov 2010 10:19:35 -0800 [thread overview]
Message-ID: <4CDED6B7.1060605@candelatech.com> (raw)
In-Reply-To: <4b2689e6064549781b072ac8956bcc1a@localhost>
On 11/12/2010 09:19 PM, Johannes Berg wrote:
>>> In nl80211_trigger_scan, if rdev->scan_req is != NULL,
>>> instead of returning EBUSY, what if we set a flag in
>>> the VIF that said "I want scan results too."
>>>
>>> Then, when whatever is scanning is finished, it would send
>>> scan results to all interested vifs.
>
> But the scans results could technically be different
> if they've been done on a different interface. Besides,
I was wondering about that...I was hoping that some results
were better than none, and that supplicant or whatever would
re-scan if it didn't find what it was looking for.
I'd also be happy to add a flag that would allow user-space
to request this feature enabled or not per-scan attempt,
and disable it by default so that no one is surprised by new
behaviour.
> you can handle it in userspace. You've been trying for
> weeks to avoid changing your userspace by changing the
> kernel, which is still the wrong approach.
From what I can tell, you are right about wpa_supplicant
controlled interfaces (perhaps requires some supplicant hacking,
but logically it can be done), but what about non-encrypted
interfaces that do not even need supplicant? It seems
user-space has very little to do with how these scan and
associated aside from setting the initial values.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-11-13 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:23 Scanning improvements for multiple VIFS Ben Greear
2010-11-13 1:00 ` Ben Greear
2010-11-13 5:19 ` Johannes Berg
2010-11-13 18:19 ` Ben Greear [this message]
2010-11-15 19:10 ` Ben Greear
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=4CDED6B7.1060605@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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.