ath9k: try more than one tid when scheduling a new aggregate
authorFelix Fietkau <nbd@openwrt.org>
Sat, 15 Jan 2011 13:30:14 +0000 (14:30 +0100)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 19 Jan 2011 16:36:10 +0000 (11:36 -0500)
commit21f28e6f0061568b2347aa7517249fc034f949b5
tree92bee48dc29fe4afdea80db428f40d37ff5619ae
parenta4d6e17d3ee0f9d12474b1692f7a0574f1aab53c
ath9k: try more than one tid when scheduling a new aggregate

Sometimes the first TID in the first AC's list is not available for forming
a new aggregate (the BAW might not allow it), however other TIDs may have
data available for sending.
Prevent a slowdown of other TIDs by going through multiple entries until
we've either hit the last one or enough AMPDUs are pending in the hardware
queue.

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