On Thu, Nov 04, 2010 at 05:11:18PM +0530, Rajkumar Manoharan wrote: > Sorry for long gap. somehow I missed your mail. During our Interop Testing, we > observed that ath9k based cards utilized the channel more frequently that others. > To ensure fair beacon distribution, BE queue parameters were set to beacon queue. Looking at interop testing results may end up being the most realistic way of getting this working properly regardless of what the standard says.. > But still I couldn't find specific WMM parameters for beacon queue except > hostap.conf which stats that > > tx_queue_beacon_aifs=2 > tx_queue_beacon_cwmin=3 > tx_queue_beacon_cwmax=7 > tx_queue_beacon_burst=1.5 Thanks for bringing those up.. I did not realize that the extra TX queue parameters were still included in hostapd.conf (well, they are not anymore.. ;-). Anyway, these were used in infrastructure BSS (i.e., by an AP), not in an IBSS. IBSS is governed by special rules in IEEE Std 802.11-2007, 11.1.2.2 like Bruno already pointed out. While management frames in general use AC_VO (until 802.11ae comes to play..), IBSS Beacon distribution is specified to follow special rules: "Calculate a random delay uniformly distributed in the range between zero and twice aCWmin x aSlotTime." where aCWmin depends on the used PHY, not some configurable AC-specific CWmin value. -- Jouni Malinen PGP id EFC895FA -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
