From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Dan Williams" <dcbw@redhat.com>
Subject: Re: technology preview: scan with cfg80211
Date: Fri, 19 Sep 2008 14:45:03 +0300 [thread overview]
Message-ID: <1ba2fa240809190445v370ee80dk316d3b474db86132@mail.gmail.com> (raw)
In-Reply-To: <1221820966.10419.81.camel@johannes.berg>
On Fri, Sep 19, 2008 at 1:42 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Fri, 2008-09-19 at 13:37 +0300, Tomas Winkler wrote:
>
>> > Hey, unfair! ;) I did leave a lot of TODOs but this wasn't one of them.
>> > You can provide a channel list and it'll scan only those (except hw scan
>> > right now but that'll be fixed once we pass the scan request struct
>> > through)
>>
>> Agree, this would be the correct approach.
>
> Yeah, but I pulled this together in about five hours :)
>
> Wrt. the SSIDs, how many SSIDs do you think we should allow scanning for
> at the same time? Three? Four? Five? I was thinking something like that,
> sending out more probe requests is probably not too great an idea.
iwlwifi HW is able to issue 10 probes per channel in a single scan.
Empirically this probably maximum of networks/SSIDs an average user
will be interested in. But we can go with less for example 5 probes
per scan if we for example round robin SSID list in background scans.
This number are based on user feedback we've been collecting for few
years. For example 2 years ago it was increased from 5 to 10 according
to user feedback.
As I understand the second approach is better as it lowers collisions
on the air and is more flexible as it's not dependent on HW limitation
(10 in iwlwifi) but requires more book keeping.
> guess we would set the default to something we decide on in mac80211's
> alloc_hw and the driver gets to overwrite it if it has hw scan offload.
Sounds good.
Tomas
next prev parent reply other threads:[~2008-09-19 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 3:18 technology preview: scan with cfg80211 Johannes Berg
2008-09-19 3:41 ` Johannes Berg
2008-09-19 8:03 ` Tomas Winkler
2008-09-19 8:56 ` Johannes Berg
2008-09-19 10:37 ` Tomas Winkler
2008-09-19 10:42 ` Johannes Berg
2008-09-19 11:45 ` Tomas Winkler [this message]
2008-09-19 11:54 ` Johannes Berg
2008-09-19 13:16 ` technology preview: scan with cfg80211 (v2) Johannes Berg
2008-09-19 14:17 ` Johannes Berg
2008-09-19 17:48 ` Luis R. Rodriguez
2008-09-19 19:18 ` Johannes Berg
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=1ba2fa240809190445v370ee80dk316d3b474db86132@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=dcbw@redhat.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