From: Luciano Coelho <coelho@ti.com>
To: "juuso.oikarinen@nokia.com" <juuso.oikarinen@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCHv4] wl12xx: Increase scan channel dwell time for passive scans
Date: Mon, 24 Jan 2011 23:36:28 +0200 [thread overview]
Message-ID: <1295904988.4430.3.camel@pimenta> (raw)
In-Reply-To: <1295848914-3765-1-git-send-email-juuso.oikarinen@nokia.com>
On Mon, 2011-01-24 at 07:01 +0100, juuso.oikarinen@nokia.com wrote:
> From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
>
> Below, mTU is milli-TU (TU/1000).
>
> The passive scan channel dwell time currently used is 30-60mTU. A typical
> beacon interval for AP's is 100TU. This leads to a ~30% worst-case probability
> of finding an AP via passive scanning.
>
> For 5GHz bands for DFS frequencies passive scanning is the only scanning
> option. Hence for these, the probability of finding an AP is very low.
>
> To fix this, increase the passive channel scan dwell times (also the early
> leave value, as 5GHz channels are still typically very silent.) Use a value
> of 100TU, because that covers most typical AP configurations.
>
> Based on testing the probability of finding an AP (100TU beacon interval) on
> a single scan round are as follows (based on 100 iterations):
>
> dwell min/max (TU) | probability
> ---------------------+------------
> 30/60 | 35%
> 60/60 | 56%
> 80/80 | 77%
> 100/100 | 100%
>
> Total scan times now and after the change:
>
> Region | Before (s) | After (s)
> -------+------------+----------
> 00 | 0.77 | 1.48
> FI | 0.95 | 2.01
> US | 0.91 | 1.76
>
> Signed-off-by: Juuso Oikarinen <juuso.oikarinen@nokia.com>
> ---
Applied and removed the mention to milli-TUs, as agreed on IRC.
Thanks Juuso!
--
Cheers,
Luca.
prev parent reply other threads:[~2011-01-24 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 6:01 [PATCHv4] wl12xx: Increase scan channel dwell time for passive scans juuso.oikarinen
2011-01-24 21:36 ` Luciano Coelho [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=1295904988.4430.3.camel@pimenta \
--to=coelho@ti.com \
--cc=juuso.oikarinen@nokia.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.