linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	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: Thu, 14 May 2009 21:06:35 +0200	[thread overview]
Message-ID: <1242327995.5799.4.camel@johannes.local> (raw)
In-Reply-To: <1242327298.4227.25.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

On Thu, 2009-05-14 at 14:54 -0400, Dan Williams wrote:

> Libertas splits scans up into 3 parts with a short return to the
> operating channel between each part.  There's nothing that requires
> cfg80211 for that to work...

Yeah that was my idea too, just return to the operating channel after
having scanned a channel or two and wait for the next beacon, and
possibly receive traffic if indicated in that beacon. It takes a bit of
synchronisation and isn't easy to implement, but it's definitely
possible.

> The problem here is that at any time an application (say, wifi location
> app) could ask for the list of access points.  If you don't scan
> periodically, all APs other than your associated AP (and others on the
> same channel) will gradually drop off because their beacons are
> received.  Hard to wifi position or get area statistics if there's only
> one AP in the list.

The other thing we should do is bump the AP list timeout, I think -- 10
seconds is very small. But then again we really need such apps to query
NM anyway.

> Secondarily, scanning is a tradeoff between better roaming latency and
> continuous high throughput.  If you don't scan, you have no idea what's
> around, and when you move and the current AP becomes marginal, you
> *have* to take the hit no matter what, so you can scan and find a new AP
> to associate with.

Yeah, that too.

> I would have though that the periodic scanning would be more of an
> annoyance when doing VOIP or SSH other latency sensitive tasks, but when
> just downloading a file, a few second drop in transfer rate gets lost in
> the bucket in the grand scheme of things.

ssh isn't too bad, at least not after I fixed the timings... before I
got very annoyed with ar9170. OTOH with VoIP it would suck to have a
small hiccup every 2 minutes -- maybe then we should postpone
indefinitely and only do it if the signal strength fluctuates?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-05-14 19:07 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 [this message]
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

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=1242327995.5799.4.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Aeolus.Yang@atheros.com \
    --cc=Gaurav.Jauhar@atheros.com \
    --cc=dcbw@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).