linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
	Juuso Oikarinen <juuso.oikarinen@nokia.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCHv3 0/2] mac80211: cfg80211: Roam trigger support
Date: Fri, 19 Mar 2010 17:15:20 -0700	[thread overview]
Message-ID: <20100320001520.GA26605@jm.kir.nu> (raw)
In-Reply-To: <20100319145636.GB9552@tuxdriver.com>

On Fri, Mar 19, 2010 at 10:56:37AM -0400, John W. Linville wrote:
> On Fri, Mar 19, 2010 at 08:59:25AM +0200, Kalle Valo wrote:
> > The idea is that wpa_supplicant will listen to these events, and will
> > enable or disable backround scan (ie. scanning for new APs when
> > associated) based on information received from the events. When the
> > connection to the AP is good enough, it can disable background scan
> > which makes it possible to save power and also get rid of latency
> > introduced by the background scan.
> > 
> > I haven't seen any implementation for wpa_supplicant yet, but we have
> > talked about that few times during the last two years.
> 
> If you can make wpa_supplicant scan less then I am sold! :-)

I would assume it is not really wpa_supplicant that is triggering too
many scans for your liking, but NetworkManager.. The goal here (at least
from my view point) is to actually make wpa_supplicant itself trigger
scans more frequently ;-).

wpa_supplicant already has a notification function just waiting to be
called from somewhere when a beacon is lost of signal strength has
changed.. That somewhere is supposed to be the driver event handler when
it receives one of these new roam trigger events. At that point,
wpa_supplicant can then figure out if it should start scanning more
frequently to find a better BSS. I would hope that this feature will
make NetworkManager eventually stop doing its constant scans (or well,
if it doesn't, I will provide an option in for wpa_supplicant to ignore
D-Bus requests for new scans.. ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2010-03-20  0:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 13:01 [RFC PATCHv3 0/2] mac80211: cfg80211: Roam trigger support Juuso Oikarinen
2010-03-17 13:01 ` [RFC PATCHv3 1/2] cfg80211: Add connection quality monitoring support to nl80211 Juuso Oikarinen
2010-03-17 16:17   ` Johannes Berg
2010-03-18  5:19     ` Juuso Oikarinen
2010-03-18 16:10       ` Johannes Berg
2010-03-19  4:43         ` Juuso Oikarinen
2010-03-19  6:39   ` Kalle Valo
2010-03-17 13:01 ` [RFC PATCHv3 2/2] mac80211: Add support for connection quality monitoring Juuso Oikarinen
2010-03-17 16:19   ` Johannes Berg
2010-03-18  5:21     ` Juuso Oikarinen
2010-03-17 16:20   ` Johannes Berg
2010-03-18  5:22     ` Juuso Oikarinen
2010-03-17 16:21   ` Johannes Berg
2010-03-17 13:22 ` [RFC PATCHv3 0/2] mac80211: cfg80211: Roam trigger support John W. Linville
2010-03-17 13:56   ` Juuso Oikarinen
2010-03-19  6:59   ` Kalle Valo
2010-03-19 14:56     ` John W. Linville
2010-03-20  0:15       ` Jouni Malinen [this message]
2010-03-20 22:34         ` 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=20100320001520.GA26605@jm.kir.nu \
    --to=j@w1.fi \
    --cc=juuso.oikarinen@nokia.com \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).