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
On Thu, Oct 7, 2010 at 3:03 AM, Bruno Randolf b...@einfach.org wrote:
On Wed October 6 2010 18:54:37 Helmut Schaa wrote:
On Tue, Oct 5, 2010 at 11:55 AM, Bruno Randolf b...@einfach.org wrote:
This adds three new values to the survey results:
* BUSY - percentage of time the channel was
On Thu, Oct 7, 2010 at 5:06 PM, Bruno Randolf b...@einfach.org wrote:
On Thu October 7 2010 15:51:49 Helmut Schaa wrote:
On Thu, Oct 7, 2010 at 3:03 AM, Bruno Randolf b...@einfach.org wrote:
On Wed October 6 2010 18:54:37 Helmut Schaa wrote:
On Tue, Oct 5, 2010 at 11:55 AM, Bruno Randolf
@lists.ath5k.org; linux-wirel...@vger.kernel.org;
linvi...@tuxdriver.com; adr...@freebsd.org; vasa...@atheros.com
Betreff: Re: [ath5k-devel] [PATCH 4/5] nl80211/mac80211: Add channel
utilization to survey
On Thu, Oct 7, 2010 at 3:03 AM, Bruno Randolf b...@einfach.org wrote:
On Wed October 6 2010 18:54
On Thu, Oct 7, 2010 at 9:06 AM, Bruno Randolf b...@einfach.org wrote:
which units do you have for the busy time? what about other drivers?
in ath[59]k we have it as cycles (which is about 1/44000 of a second,
depending on the mode). so it counts up rather fast.
We've got the busy time in [us]
On Tue, Oct 5, 2010 at 11:55 AM, Bruno Randolf b...@einfach.org wrote:
This adds three new values to the survey results:
* BUSY - percentage of time the channel was busy
* BUSY_TX - percentage of time spent transmitting frames
* BUSY_RX - percentage of time spent receiving frames
Does
On Wed, Oct 6, 2010 at 6:03 PM, Bruno Randolf b...@einfach.org wrote:
On Wed October 6 2010 18:54:37 Helmut Schaa wrote:
On Tue, Oct 5, 2010 at 11:55 AM, Bruno Randolf b...@einfach.org wrote:
This adds three new values to the survey results:
* BUSY - percentage of time the channel was
This adds three new values to the survey results:
* BUSY - percentage of time the channel was busy
* BUSY_TX - percentage of time spent transmitting frames
* BUSY_RX - percentage of time spent receiving frames
They are defined to be a percentage of time, normalized to 255. That way they
On Wed October 6 2010 07:36:30 Luis R. Rodriguez wrote:
On Tue, Oct 5, 2010 at 2:55 AM, Bruno Randolf b...@einfach.org wrote:
This adds three new values to the survey results:
* BUSY - percentage of time the channel was busy
* BUSY_TX - percentage of time spent transmitting frames
*