From: Kalle Valo <kalle.valo@iki.fi>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: 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 08:59:25 +0200 [thread overview]
Message-ID: <87aau4dcfm.fsf@purkki.valot.fi> (raw)
In-Reply-To: <20100317132236.GC2990@tuxdriver.com> (John W. Linville's message of "Wed\, 17 Mar 2010 09\:22\:36 -0400")
"John W. Linville" <linville@tuxdriver.com> writes:
> On Wed, Mar 17, 2010 at 03:01:15PM +0200, Juuso Oikarinen wrote:
>> To implement good performance WLAN roaming, it is not sufficient to start
>> scanning for other available AP's only after the currently serving association
>> is lost.
>>
>> The entity controlling the roaming will need to get indication of a
>> deteriorating WLAN connection in order to start preparing for roaming already
>> before the serving association is lost. This way, it can roam to a better AP
>> perhaps even before the serving association becomes too bad in quality.
[...]
> Any idea what other hardware (besides libertas) supports this
> concept?
I myself only know that wl1251 and wl1271 have this. But I wouldn't be
surprised if recent Intel designs also support it. It's a quite useful
feature, I would say that it's even a must-have feature for power
consumption critical devices.
And even if hardware wouldn't support this, having a host-based
implementation host would make it easier for wpa_supplicant.
> Do you anticipate adding a host-based implementation to mac80211?
I think we need a support for this, otherwise testing is next to
impossible because of small number of wl1271 and wl1251 upstream
users. I would prefer to have the host-based implementation right from
the start.
> Is RSSI really a useful enough indicator for this function?
Yes, it actually is. I implemented a similar hack for Nokia N900 which
is now in use by real customers. I just had to use WE custom events
due to project schedule constraints.
But I'm sure in the future we use different attributes for this, for
example retransmissions.
> Will applications actually use it?
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.
--
Kalle Valo
next prev parent reply other threads:[~2010-03-19 6:59 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 [this message]
2010-03-19 14:56 ` John W. Linville
2010-03-20 0:15 ` Jouni Malinen
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=87aau4dcfm.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=juuso.oikarinen@nokia.com \
--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).