All of lore.kernel.org
 help / color / mirror / Atom feed
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: [PATCHv2] wl12xx: Increase scan channel dwell time for passive scans
Date: Fri, 21 Jan 2011 15:35:49 +0200	[thread overview]
Message-ID: <1295616949.1925.118.camel@pimenta> (raw)
In-Reply-To: <1295332325-26477-1-git-send-email-juuso.oikarinen@nokia.com>

Hi Juuso,

Just a quick comment/question:


On Tue, 2011-01-18 at 07:32 +0100, juuso.oikarinen@nokia.com wrote:
> From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
> 
> The passive scan channel dwell time currently used is 30ms-60ms. A typical
> beacon interval for AP's is 100ms. This leads to a ~30% worst-case probability
> of finding an AP via passive scanning.

The beacon intervals are defined in TUs.


> 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 100ms, because that covers most typical AP configurations.

In the firmware API, the dwell times are expressed in milli-TUs.  So I
guess here you mean "use a value of 100 TUs", isn't it?


> Based on testing the probability of finding an AP (102.4ms beacon interval) on
> a single scan round are as follows (based on 100 iterations):

Here you use milliseconds for the AP beacon interval.  102.4ms is 100
TUs, so that's correct.

It's just a bit confusing because of the slight difference between TUs
and msecs.  Gery was wondering why you were using 100ms if the most
common beacon interval is 102.4ms (100 TUs).  Of course, you're actually
using 100 TUs, so it's fine.

I just think it's easier to follow if you forget msecs and use only TUs
in your explanation.


-- 
Cheers,
Luca.


  reply	other threads:[~2011-01-21 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  6:32 [PATCHv2] wl12xx: Increase scan channel dwell time for passive scans juuso.oikarinen
2011-01-21 13:35 ` Luciano Coelho [this message]
2011-01-24  5:53   ` Juuso Oikarinen

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=1295616949.1925.118.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.