linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Helmut Schaa <hschaa@suse.de>
Cc: Jouni Malinen <j@w1.fi>,
	Holger Schurig <hs4233@mail.mn-solutions.de>,
	linux-wireless@vger.kernel.org
Subject: Re: Pondering: how to improve mac80211 roaming ...
Date: Wed, 13 Aug 2008 08:49:15 -0400	[thread overview]
Message-ID: <1218631755.29370.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200808131426.55673.hschaa@suse.de>

On Wed, 2008-08-13 at 14:26 +0200, Helmut Schaa wrote:
> Am Dienstag, 12. August 2008 17:42:23 schrieb Jouni Malinen:
> > On Tue, Aug 12, 2008 at 02:40:23PM +0200, Helmut Schaa wrote:
> > > JFYI I already started to rework the existing scan code in mac80211
> > > (software scan) to do something like background scanning:
> > >
> > > 1) notify current AP about leaving the channel
> > > 2) scan one channel
> >
> > It might be useful to leave this "one" as a parameter to allow easy
> > experiments with scanning more than one channel at a time to reduce
> > latency.
> 
> Good point.
> 
> > Ideally, this--along the interval for background scans--could 
> > be something that is dynamically changed based on the expected traffic
> > pattern. Whenever there is lot of data traffic being (mostly
> > successfully) transmitted, it would be beneficial not to jump to other
> > channels as frequently or for as long a time. If there has not been any
> > data transmission for some time, it may be more acceptable to scan more
> > frequently and to remain away from the operational channel for longer
> > periods of time. Though, we should also keep in mind that background
> > scans are going to increase power consumption on otherwise inactive
> > situation, so setting a suitable policy for this can get quite complex.
> 
> It might even be beneficial to cancel a currently active background scan once 
> the TX queue is filling up and report the already gathered information to the 
> user space.

If that's the case, we should also then have a response to the original
scan request (or broadcast netlink message with the original request's
cookie) that says "scan canceled" so that the requester can handle that.

dan


  reply	other threads:[~2008-08-13 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  6:38 Pondering: how to improve mac80211 roaming Holger Schurig
2008-08-12  8:22 ` Jouni Malinen
2008-08-12  9:56   ` Holger Schurig
2008-08-12 12:40   ` Helmut Schaa
2008-08-12 15:42     ` Jouni Malinen
2008-08-12 17:56       ` Luis R. Rodriguez
2008-08-13  6:41         ` Holger Schurig
2008-08-13  6:50           ` Jouni Malinen
2008-08-13 12:26       ` Helmut Schaa
2008-08-13 12:49         ` Dan Williams [this message]
2008-08-13 12:53           ` Helmut Schaa
2008-08-13 14:18         ` Holger Schurig
2008-08-13 14:26           ` Helmut Schaa
2008-08-13  6:52   ` Holger Schurig
2008-08-13 12:02     ` Dan Williams
2008-08-13 14:28       ` Holger Schurig
2008-08-14  7:05   ` Kalle Valo
2008-08-14  8:25     ` Jouni Malinen
2008-08-14 18:30       ` Dan Williams
2008-08-14  6:42 ` Kalle Valo

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=1218631755.29370.1.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=hschaa@suse.de \
    --cc=j@w1.fi \
    --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;
as well as URLs for NNTP newsgroup(s).