linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCHv3 0/2] mac80211: cfg80211: Roam trigger support
Date: Wed, 17 Mar 2010 09:22:36 -0400	[thread overview]
Message-ID: <20100317132236.GC2990@tuxdriver.com> (raw)
In-Reply-To: <1268830877-5162-1-git-send-email-juuso.oikarinen@nokia.com>

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.
> 
> These patches propose an implementation facilitating this using a simple RSSI
> threshold and hysteresis approach.
> 
> These patches add a nl80211 interface for simply configuring a rssi threshold
> and hysteresis value to facilitate very basic connection quality monitoring.
> 
> For the triggering, these patches currently rely on HW support, host based
> triggering is not implemented, but could be added later if needed.
> 
> These patches have been tested with the wl1271 driver.
> 
> Thanks in advance for your comments and suggestions.
> 
> Juuso Oikarinen (2):
>   cfg80211: Add connection quality monitoring support to nl80211
>   mac80211: Add support for connection quality monitoring

Any idea what other hardware (besides libertas) supports this concept?
Do you anticipate adding a host-based implementation to mac80211?

Is RSSI really a useful enough indicator for this function?
Will applications actually use it?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2010-03-17 13:30 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 ` John W. Linville [this message]
2010-03-17 13:56   ` [RFC PATCHv3 0/2] mac80211: cfg80211: Roam trigger support Juuso Oikarinen
2010-03-19  6:59   ` Kalle Valo
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=20100317132236.GC2990@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=juuso.oikarinen@nokia.com \
    --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).