From: Jouni Malinen <j@w1.fi>
To: Ben Greear <greearb@candelatech.com>
Cc: "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 17:03:16 -1000 [thread overview]
Message-ID: <20100915030316.GB30253@jm.kir.nu> (raw)
In-Reply-To: <4C8EB03D.7070808@candelatech.com>
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?
If you want to limit scans a single channel in some special use cases,
you should be able to do that in user space, too, at least for the
initial scan before connection. As a future optimization, we should
somehow be able to merge scan requests from multiple VIFs into a single
one, i.e., share the results from a single scan to multiple VIFs..
PS.
It would be easier to comment on the changes if you were to inline them
instead of attaching the file..
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2010-09-15 3:03 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 [this message]
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
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=20100915030316.GB30253@jm.kir.nu \
--to=j@w1.fi \
--cc=greearb@candelatech.com \
--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.