tree a75e43aad931ffdaea889af7b2275f12a16f077a
parent 6db3786aee36b32e5ed072ed67fad6d5341b0991
author Ivo van Doorn <IvDoorn@gmail.com> 1212785594 +0200
committer John W. Linville <linville@tuxdriver.com> 1213460276 -0400

rt2x00: Don't kick TX queue after each frame

TX queues shouldn't be kicked after each frame that is put into the
queue.  This could cause problems during RTS and CTS-to-self as well
as with fragmentation. In all those cases you want all frames to be
send out in a single burst. Off course we shouldn't let the queue fill
up entirely, thus we introduce a 10% threshold which, when reached,
will force the frames to be send out regardless of the frame.

In addition we should prevent queues to become full in such a way
that the tx() handler can fail. Instead of stopping the queue when
it is full, we should stop it when it is below the threshold.

Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>