ath9k: limit multicast buffer hardware queue depth
authorFelix Fietkau <nbd@openwrt.org>
Fri, 7 Jun 2013 16:12:02 +0000 (18:12 +0200)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 12 Jun 2013 19:06:49 +0000 (15:06 -0400)
commit59505c02e106ce9388d816799cd64b0405f98f2f
treeebf04dcc2b99f53bf6e4af96cb9891c8b96b7fe0
parent86a22acfcb40ed9cf4ceee789b45da6a3314ed77
ath9k: limit multicast buffer hardware queue depth

The CAB (Content after Beacon) queue is used for beacon-triggered
transmission of buffered multicast frames. If lots of multicast frames
were buffered and this queue fills up, it drowns out all regular
traffic. To limit the damage that buffered traffic can do, try to limit
the queued data to becaon_interval / 8.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath/ath9k/ath9k.h
drivers/net/wireless/ath/ath9k/beacon.c
drivers/net/wireless/ath/ath9k/xmit.c