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] since the last read (the register is cleared on read). > some absolute cumulative value would be better, so several userspace processes > can poll and do their own averaging or percentage calculations. > > but which units to use? what would be a good way of solving that? > any ideas??? That's what 802.11-2007 tells us in regard to the BSS Load element: <citation> ((channel busy time/(dot11ChannelUtilizationBeaconIntervals * dot11BeaconPeriod * 1024)) * 255), where channel busy time is defined to be the number of microseconds during which the CS mechanism, as defined in 9.2.1, has indicated a channel busy indication, and the MIB attribute dot11ChannelUtilization- BeaconIntervals represents the number of consecutive beacon intervals during which the channel busy time is measured. The default value of dot11ChannelUtilizationBeaconIntervals is defined in Annex D. </citation> So, I guess it makes sense to just return the calculated channel utilization value (u8) and keep it up to date within the driver. mac80211 could pass dot11ChannelUtilizationBeaconIntervals (using the default of 16 for now) to the drivers and the drivers would report the calculated value. Helmut _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
