On 2010-09-21 2:08 PM, Ben Greear wrote: > On 09/21/2010 03:10 AM, Felix Fietkau wrote: >> On 2010-09-21 7:25 AM, Ben Greear wrote: >>> I think I have narrowed down some problems I see when I create >>> two STA interfaces on the same radio and associate with the >>> same AP. >>> >>> I'm using wireless-testing plus some patches to the rx logic >>> I posted earlier. >>> >>> It appears that the ath9k NIC does not transport AMPDUs properly, >>> and after a few seconds, it's backlog is exhausted and the queues >>> are stopped in ath_tx_start. >> ath9k currently looks up the sta by hw and not by vif on tx completion. >> That completely breaks aggregation in such a setup. Unfortunately I >> don't know an easy way to fix this yet. >> >> This will be fixed by my sw aggregation rewrite, but I don't know when >> I'll get that completed yet. > > If you have any more details on this, please let me know. I'm going to > attempt to fix it...I certainly have a good test case :) ath_tx_complete_aggr completes an A-MPDU frame, which typically triggers the release of the next A-MPDU to the hw queue. To keep track of the Block ACK window, it needs to look up the TID, for which it needs a STA pointer. At that level, the driver typically doesn't have access to the vif.
It might be possible to fix this by adding another sta lookup helper function in mac80211 that takes another address argument for the BSSID, so that it can get the sta entry for the correct vif. I don't know if Johannes wants something like that though. - Felix _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
