From: Ben Greear <greearb@candelatech.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Jouni Malinen <j@w1.fi>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated.
Date: Tue, 14 Sep 2010 22:49:01 -0700 [thread overview]
Message-ID: <4C905E4D.7060707@candelatech.com> (raw)
In-Reply-To: <1284529613.10728.32.camel@dcbw.foobar.com>
On 09/14/2010 10:46 PM, Dan Williams wrote:
> On Tue, 2010-09-14 at 22:30 -0700, Ben Greear wrote:
>> On 09/14/2010 08:03 PM, Jouni Malinen wrote:
>>> On Mon, Sep 13, 2010 at 04:14:05PM -0700, Ben Greear wrote:
>>>> This patch aims to decrease channel switching when there is at least one
>>>> interface associated. This should help multiple station interfaces co-exist
>>>> on the same hardware, especially in WPA mode.
>>>
>>> If I understood the change correctly, it would prevent running full
>>> scans when in associated state. That does not sound reasonable behavior
>>> and scanning should not cause an association to be lost. Did I miss
>>> something or what exactly is this trying to do?
>>
>> That's pretty much what I'm trying to do. We had similar code in
>> our 2.6.31 kernel with ath5k. Imagine getting 50 virtual stations
>> started with WPA and all of them trying to scan all channels at once!
>> Most got timeouts, and one scanning would disrupt traffic on the others.
>> And, the hardware can only associate on a single channel anyway, so getting
>> scan results for other channels doesn't do a great deal of good.
>>
>> With current ath9k, I see DMA timeouts and other nasty things (without
>> that patch applied) when trying to bring up two VIFs with WPA.
>>
>> I think for the multi-VIF scenario, it should scan the single associated
>> channel by default, but it would be nice to allow full scans on demand.
>> (I would very much like to work with standard wpa_supplicant, but if hacking it
>> is the only way, then I can attempt that.)
>
> Allowing full scans on demand (ie when userspace requests it) is a must.
> Even in multi-VIF mode.
So, something like 'iw sta1 scan all' to force scanning all,
with 'iw sta1 scan' just returning results for associated channel
in multi-vif scenario?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-15 5:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:14 RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated Ben Greear
2010-09-15 3:03 ` Jouni Malinen
2010-09-15 5:30 ` Ben Greear
2010-09-15 5:46 ` Dan Williams
2010-09-15 5:48 ` Dan Williams
2010-09-15 5:49 ` Ben Greear [this message]
2010-09-15 10:16 ` Johannes Berg
2010-09-15 14:21 ` Ben Greear
2010-09-15 14:24 ` Johannes Berg
2010-09-15 15:32 ` Ben Greear
2010-09-15 15:37 ` Johannes Berg
2010-09-15 16:12 ` Ben Greear
2010-09-15 20:31 ` Jouni Malinen
2010-09-15 21:04 ` Luis R. Rodriguez
2010-09-16 0:11 ` 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=4C905E4D.7060707@candelatech.com \
--to=greearb@candelatech.com \
--cc=dcbw@redhat.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 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).