From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bruno Randolf <br1@einfach.org>,
linville@tuxdriver.com, nbd@openwrt.org,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
adrian@freebsd.org, vasanth@atheros.com,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Jonathan Guerin <jonathan@guerin.id.au>
Subject: Re: [PATCH 4/5] nl80211/mac80211: Add channel utilization to survey
Date: Fri, 8 Oct 2010 19:41:06 +0200 [thread overview]
Message-ID: <201010081941.07134.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <1286437954.3657.17.camel@jlt3.sipsolutions.net>
Am Donnerstag 07 Oktober 2010 schrieb Johannes Berg:
> On Thu, 2010-10-07 at 09:44 +0200, Helmut Schaa wrote:
>
> > So, I guess it makes sense to just return the calculated channel
> > utilization value (u8)
> > and keep it up to date within the driver.
>
> Not good, that means drivers implementing this will have to wake the CPU
> to do calculations even if nobody cares.
You're obviously right. But that would be the same if mac80211 would do
the calculation. And if we would only calculate it when the survey is
requested the measurement window could be very large or very small which
both might be unwanted.
This could also introduce problems related to register overflows. Since
on rt2800 the register (32bit) is in units of [us] it would overflow after
a bit more then one hour making the calculation flawed in that (maybe
unusual) case.
Nevertheless I fully agree that it doesn't make sense to always calculate
the busy time values if nobody actually needs it. But if somebody cares it
would be nice to have it as a percentage value.
Helmut
next prev parent reply other threads:[~2010-10-08 17:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 9:55 [PATCH 1/5] ath: Add common function for reading cycle counters Bruno Randolf
2010-10-05 9:55 ` [PATCH 2/5] ath5k: Use common cycle counters for ANI Bruno Randolf
2010-10-05 9:55 ` [PATCH 3/5] ath9k: Use common cycle counters Bruno Randolf
2010-10-05 20:14 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-06 1:10 ` Bruno Randolf
2010-10-06 1:13 ` Luis R. Rodriguez
2010-10-06 1:18 ` Luis R. Rodriguez
2010-10-06 2:00 ` Bruno Randolf
2010-10-06 2:15 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-05 9:55 ` [PATCH 4/5] nl80211/mac80211: Add channel utilization to survey Bruno Randolf
2010-10-05 22:36 ` Luis R. Rodriguez
2010-10-06 2:35 ` Bruno Randolf
2010-10-06 9:54 ` Helmut Schaa
2010-10-07 1:03 ` Bruno Randolf
2010-10-07 3:02 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-07 6:51 ` Helmut Schaa
2010-10-07 7:06 ` Bruno Randolf
2010-10-07 7:35 ` Jonathan Guerin
2010-10-07 7:44 ` Helmut Schaa
2010-10-07 7:52 ` Johannes Berg
2010-10-08 17:41 ` Helmut Schaa [this message]
2010-10-05 9:55 ` [PATCH 5/5] ath5k: Add busy ratios to survey data Bruno Randolf
2010-10-05 22:38 ` Luis R. Rodriguez
2010-10-06 2:25 ` Bruno Randolf
2010-10-06 2:45 ` Felix Fietkau
2010-10-06 2:50 ` Bruno Randolf
2010-10-06 14:13 ` Luis R. Rodriguez
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=201010081941.07134.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=adrian@freebsd.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=jonathan@guerin.id.au \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=nbd@openwrt.org \
--cc=vasanth@atheros.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).