From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH, v2]: nl80211: report age of scan results
Date: Thu, 24 Sep 2009 12:29:19 +0200 [thread overview]
Message-ID: <1253788159.3868.23.camel@johannes.local> (raw)
In-Reply-To: <200909241221.01456.hs4233@mail.mn-solutions.de>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
On Thu, 2009-09-24 at 12:21 +0200, Holger Schurig wrote:
> Linux keeps scan results up to 15 seconds. This can be a problem for fast
> moving clients: they get back stale data. But if the kernel reports the age
> of the BSS items, then user-space can simply weed out old entries by itself.
>
> Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
Fine with me, I don't care if there is a #define or not.
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
>
> ---
>
> v2: renamed NL80211_BSS_AGE_MS to NL80211_BSS_SEEN_MS_AGO to underline that
> it's a relativene time
>
> --- linux-wl.orig/include/linux/nl80211.h
> +++ linux-wl/include/linux/nl80211.h
> @@ -1277,6 +1277,7 @@
> * @NL80211_BSS_SIGNAL_UNSPEC: signal strength of the probe response/beacon
> * in unspecified units, scaled to 0..100 (u8)
> * @NL80211_BSS_STATUS: status, if this BSS is "used"
> + * @NL80211_BSS_SEEN_MS_AGO: age of this BSS entry in ms
> * @__NL80211_BSS_AFTER_LAST: internal
> * @NL80211_BSS_MAX: highest BSS attribute
> */
> @@ -1291,6 +1292,7 @@
> NL80211_BSS_SIGNAL_MBM,
> NL80211_BSS_SIGNAL_UNSPEC,
> NL80211_BSS_STATUS,
> + NL80211_BSS_SEEN_MS_AGO,
>
> /* keep last */
> __NL80211_BSS_AFTER_LAST,
> --- linux-wl.orig/net/wireless/nl80211.c
> +++ linux-wl/net/wireless/nl80211.c
> @@ -3105,6 +3105,8 @@
> NLA_PUT_U16(msg, NL80211_BSS_BEACON_INTERVAL, res->beacon_interval);
> NLA_PUT_U16(msg, NL80211_BSS_CAPABILITY, res->capability);
> NLA_PUT_U32(msg, NL80211_BSS_FREQUENCY, res->channel->center_freq);
> + NLA_PUT_U32(msg, NL80211_BSS_SEEN_MS_AGO,
> + jiffies_to_msecs(jiffies - intbss->ts));
>
> switch (rdev->wiphy.signal_type) {
> case CFG80211_SIGNAL_TYPE_MBM:
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-09-24 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:21 [PATCH, v2]: nl80211: report age of scan results Holger Schurig
2009-09-24 10:29 ` Johannes Berg [this message]
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=1253788159.3868.23.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=hs4233@mail.mn-solutions.de \
--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