> Say a station enables aggregation on a low-priority TID, manages to fill > the hw queue because high-prio frames are eating up all the airtime and > then disables aggregation again. Now another station enables aggregation > on a high-priority TID, and gets assigned to the same hw queue. Now > frames for that station will be stalled, no? Seems like a bug to me. Never mind, the queue won't get reassigned. I was just confused by a bunch of superfluous code in iwl-tx.c. You cannot ever run into having IWL_EMPTYING_HW_QUEUE_ADDBA set because you wait for the queue to drain before fully disabling it. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
