From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Aeolus.Yang@atheros.com,
Senthil Balasubramanian <senthilkumar@atheros.com>,
Gaurav.Jauhar@atheros.com
Subject: Re: Scan while TX/RX'ing a lot of data
Date: Mon, 18 May 2009 11:35:24 -0400 [thread overview]
Message-ID: <1242660924.6530.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1242478137.10005.63.camel@johannes.local>
On Sat, 2009-05-16 at 14:48 +0200, Johannes Berg wrote:
> On Fri, 2009-05-15 at 19:15 -0400, Dan Williams wrote:
>
> > Well, what does "background scan" mean? mac80211 will obviously accept
> > beacons from APs on the same channel and happily add them to the scan
> > list.
>
> Only if powersave/beacon filtering isn't enabled. Actually, mac80211
> does beacon filtering itself now, so I don't think this happens any more
> (I did that on purpose so people don't really rely on the former
> behaviour)
>
> > But a background scan would imply that the card itself is taking
> > over the decision about when to jump around and scan, basically the same
> > thing NM is doing, right? When would the card/stack decided to
> > background scan, and what channels would it background scan on? If it
> > doesn't do more or less all passive channels, then it wouldn't be that
> > useful for figuring out the site survey data.
>
> I would think that mac80211, while asked to scan when associated, could
> simply do something like calculating how long it can go off-channel
> under the current QoS requirements, and then go off-channel for that,
> wait for the next on-channel beacon and some traffic, scan the next
> channel(s) again etc.
Yeah, that sounds like it would work.
Dan
prev parent reply other threads:[~2009-05-18 15:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 17:52 Scan while TX/RX'ing a lot of data Luis R. Rodriguez
2009-05-14 18:54 ` Dan Williams
2009-05-14 19:06 ` Johannes Berg
2009-05-14 20:50 ` Dan Williams
2009-05-14 20:53 ` Johannes Berg
2009-05-14 19:07 ` Luis R. Rodriguez
2009-05-14 20:57 ` Dan Williams
2009-05-14 21:26 ` Luis R. Rodriguez
2009-05-14 22:17 ` Luis R. Rodriguez
2009-05-16 6:12 ` Luis R. Rodriguez
2009-05-16 6:15 ` Luis R. Rodriguez
2009-05-16 12:57 ` Johannes Berg
2009-05-18 12:38 ` John W. Linville
2009-05-18 17:52 ` Luis R. Rodriguez
2009-05-18 13:43 ` Helmut Schaa
2009-05-19 9:06 ` Johannes Berg
2009-05-20 11:41 ` Helmut Schaa
2009-05-20 11:44 ` Johannes Berg
2009-05-20 13:43 ` Helmut Schaa
2009-05-20 13:53 ` Johannes Berg
2009-05-18 18:06 ` Luis R. Rodriguez
2009-05-19 9:09 ` Johannes Berg
2009-05-15 8:11 ` Holger Schurig
2009-05-15 8:31 ` Johannes Berg
2009-05-15 23:15 ` Dan Williams
2009-05-16 12:48 ` Johannes Berg
2009-05-18 15:35 ` Dan Williams [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=1242660924.6530.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Aeolus.Yang@atheros.com \
--cc=Gaurav.Jauhar@atheros.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=senthilkumar@atheros.com \
/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.