From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
David Quan <David.Quan@atheros.com>,
Michael Green <Michael.Green@atheros.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Further improvements to the software scan implementation
Date: Thu, 16 Jul 2009 09:09:14 -0700 [thread overview]
Message-ID: <43e72e890907160909t6bc5809ued28581e1a7a668f@mail.gmail.com> (raw)
In-Reply-To: <200907161138.58874.helmut.schaa@gmail.com>
Adding David Quan and Michael Green, my reply in-line below.
On Thu, Jul 16, 2009 at 2:38 AM, Helmut
Schaa<helmut.schaa@googlemail.com> wrote:
> Hi,
>
> as already discussed with Johannes we can further optimize the scan
> implementation by allowing (on an active channel) to send probes as
> soon as any other frame is received (and updated the NAV) instead of
> ever waiting 30ms.
>
> Another optimization I thought of while reading [1] would be to take the
> same approach as Intel in their ucode. If a frame is received while
> scanning a passive channel switch to active scan mode and send out probes.
> That should allow us to shorten the time needed to stay on that channel.
> Luis, do you think this is ok in regard to regulatory restrictions?
Good question. We already enable active scanning if a beacon is
received from an AP and are world roaming. We do this in mac80211
through a beacon regulatory hint to the wireless core --
regulatory_hint_found_beacon(). The assumption of the beacon
regulatory hint is that APs *must* be compliant, and some cards world
roam therefore only allowing passive scan on some channels, when you
receive a beacon from an AP on a non-DFS channel or channel 12-14 it
is safe to assume you can actively scan and beacon on that same
channel. Reason for the passive scan flag to exist is for a way to
enable some cards to world roam on some channels. Because all APs must
beacon and since we will lift this passive scan flag during an initial
scan I am inclined to believe we shouldn't bother with processing
other 802.11 frames. So in summary I'd suggest to not do this because:
1) We already have the beacons during an initial scan
2) We'd have to figure out a way to ensure the frame was indeed from an AP
Luis
> Thanks,
> Helmut
>
> [1] http://sourceforge.net/mailarchive/forum.php?thread_name=200907061428.55840.jung%40ecos.de&forum_name=ipw3945-devel
>
prev parent reply other threads:[~2009-07-16 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 9:38 Further improvements to the software scan implementation Helmut Schaa
2009-07-16 9:46 ` Johannes Berg
2009-07-16 14:15 ` Johannes Berg
2009-07-16 16:09 ` Luis R. Rodriguez [this message]
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=43e72e890907160909t6bc5809ued28581e1a7a668f@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=David.Quan@atheros.com \
--cc=Michael.Green@atheros.com \
--cc=helmut.schaa@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox