From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
lrodriguez@atheros.com, br1@einfach.org
Subject: Re: [PATCH 1/3] cfg80211: add channel utilization stats to the survey command
Date: Sat, 9 Oct 2010 14:17:25 +0200 [thread overview]
Message-ID: <201010091417.25727.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <1286584771-76663-1-git-send-email-nbd@openwrt.org>
Am Samstag 09 Oktober 2010 schrieb Felix Fietkau:
> Using these, user space can calculate a relative channel utilization
> with arbitrary intervals by regularly taking snapshots of the survey
> results.
What if you've got multiple consumers, wouldn't that mess up the
survey results?
I mean, for example mac80211 and/or hostapd might want to use the busy time
statistics for the BSS load IE while a different userspace process might
want to monitor the channel utilization in order to detect a worsening
channel condition.
If the consumers happen to use the same interval and request the survey
very soon after each other one consumer will get the values on a nice (close
to the query interval) time base while the other one will get the values
based on a very small interval (which might lower the value's
representativeness).
Helmut
next prev parent reply other threads:[~2010-10-09 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 0:39 [PATCH 1/3] cfg80211: add channel utilization stats to the survey command Felix Fietkau
2010-10-09 0:39 ` [PATCH 2/3] ath9k: add compile time checking for the size of the channel list Felix Fietkau
2010-10-09 0:39 ` [PATCH 3/3] ath9k: implement channel utilization stats for survey Felix Fietkau
2010-10-10 16:21 ` [PATCH v2 " Felix Fietkau
2010-10-09 12:17 ` Helmut Schaa [this message]
2010-10-09 13:08 ` [PATCH 1/3] cfg80211: add channel utilization stats to the survey command Felix Fietkau
2010-10-09 15:37 ` Helmut Schaa
2010-10-09 16:32 ` Felix Fietkau
2010-10-09 18:45 ` Helmut Schaa
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=201010091417.25727.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=nbd@openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.