From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: "Dan Williams" <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, Helmut Schaa <hschaa@suse.de>
Subject: Re: [RFC] mac80211: notify the user space about low signal quality
Date: Tue, 16 Sep 2008 10:50:41 +0200 [thread overview]
Message-ID: <200809161050.41482.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <87fxo0zee1.fsf@nokia.com>
On Tuesday 16 September 2008 10:25:10 Kalle Valo wrote:
>> My main problem is that adding a beacon threshold to mac80211
>> isn't a
> Still I don't see a problem here, all the mac80211 drivers
> should already now report similar signal strenght to the
> mac80211 in comparable level.
And we could later allow something similar to "iwconfig ethX sens
Y" to modify the the threshold (or whatever else we use, even
some arbitrary calculated quality value). The possibility to
modify this would allow the user to define how eager mac80211 is
when it comes to roaming.
I actually believe that we shouldn't use Quality as roaming
decision base. From what I know, Quality also counts in
re-transmissions, transfer speed (1 MBit/s is worse then 54
MBit/s) and whatever else. Therefore you can calculate quality
only for the current conection.
But when you scan, you only see signal strength and/or SNR of the
APs in sight. You won't know their quality of those APs.
But you could compare your current signal strength and/or SNR to
the signal strength/SNR of the APs in sight.
That would mean that you can use the Quality still for a
decision "Should I do a background scan or not?". But you cannot
use it for a decision "Should I switch to this AP or not?".
And so I wonder why I should use quality in the first place if it
brings me only so far ...
next prev parent reply other threads:[~2008-09-16 8:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 12:16 More thoughts about roaming Helmut Schaa
2008-09-15 12:29 ` [RFC] Implement basic background scanning Helmut Schaa
2008-09-15 14:32 ` Michael Buesch
2008-09-15 14:40 ` Helmut Schaa
2008-09-15 15:59 ` Johannes Berg
2008-09-15 16:35 ` Helmut Schaa
2008-09-16 8:43 ` Kalle Valo
2008-09-16 9:10 ` Johannes Berg
2008-09-16 9:20 ` Helmut Schaa
2008-09-16 11:06 ` Johannes Berg
2008-09-16 9:15 ` Tomas Winkler
2008-09-15 12:35 ` [RFC] mac80211: notify the user space about low signal quality Helmut Schaa
2008-09-15 14:07 ` Dan Williams
2008-09-15 14:34 ` Helmut Schaa
2008-09-15 15:28 ` Dan Williams
2008-09-15 16:45 ` Helmut Schaa
2008-09-16 1:21 ` Luis R. Rodriguez
2008-09-16 7:41 ` Helmut Schaa
2008-09-16 8:07 ` Kalle Valo
2008-09-16 8:12 ` Johannes Berg
2008-09-16 8:55 ` Kalle Valo
2008-09-23 18:21 ` John W. Linville
2008-09-16 8:00 ` Kalle Valo
2008-09-16 7:57 ` Kalle Valo
2008-09-15 15:10 ` Holger Schurig
2008-09-15 15:19 ` Dan Williams
2008-09-16 8:25 ` Kalle Valo
2008-09-16 8:50 ` Holger Schurig [this message]
2008-09-16 9:25 ` Helmut Schaa
2008-09-16 9:32 ` Helmut Schaa
2008-09-16 10:23 ` Holger Schurig
2008-09-15 15:17 ` Holger Schurig
2008-09-16 7:53 ` Kalle Valo
2008-09-15 12:41 ` [RFC] wpa_supplicant: trigger a scan if signal quality is low Helmut Schaa
2008-09-15 13:59 ` More thoughts about roaming Dan Williams
2008-09-15 14:18 ` Helmut Schaa
2008-09-15 14:45 ` Dan Williams
2008-09-16 7:09 ` 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=200809161050.41482.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=hschaa@suse.de \
--cc=kalle.valo@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).