On 9 June 2016 at 19:56, Adrian Chadd <adr...@freebsd.org> wrote: > hi, > > I've noticed something reasonably quirky with the AR9380 and later > EDMA engine and I'd like to see if anyone else has seen it with ath9k. > > It /looks/ like the TXOP gating for burstTime (ie, WMM bursts) is > gated by a TX FIFO entry. Ie, if you queue 8 separate TX FIFO entries, > each with a single MPDU, then you end up only getting one frame per > burst window. >
So it looks like it's not specifically TXOP gating, but it's frame scheduling gating and chantime gating. I need to go see what's going on in more detail. Ie, if I have a TXOP burst with lockout and it's frame scheduling is beacon gated (eg, like CAB queue is setup) then only one TX FIFO entry seems to get ungated, and then things stay locked out. If I'm pushing frames into the queue then things seem to get serviced, but if the queue is full then nothing extra gets serviced. -adrian _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
