On 2012-12-03 3:13 PM, Andreas Hartmann wrote: > Hi Stanislaw! > > Stanislaw Gruszka wrote: >> Commit f0425beda4d404a6e751439b562100b902ba9c98 "mac80211: retry sending >> failed BAR frames later instead of tearing down aggr" caused regression >> on rt2x00 hardware (connection hangs). > > This patch caused a problem, too, with carl9170 > (http://thread.gmane.org/gmane.linux.kernel.wireless.general/92203/focus=92376). > How did they fix it (the thread unfortunately ends without any solution > / patch). > >> This regression was fixed by >> commit be03d4a45c09ee5100d3aaaedd087f19bc20d01 "rt2x00: Don't let >> mac80211 send a BAR when an AMPDU subframe fails". But the letter >> commit, caused yet another problem reported in >> https://bugzilla.kernel.org/show_bug.cgi?id=42828#c22 > > This already was a workaround as stated in the removed comment: "TODO: > Need to tear down BA session here if not successful." > > My general question is: > Is the behaviour of f0425beda spec conform? Is it implemented correctly > and w/o demanding any special hardware feature? If both questions can be > answered with yes, rt2x00 should be fixed to get the same behaviour working. > > If f0425beda isn't spec conform or if it expects special hardware > features, it would be a more or less a ath9k specific "solution", which > should be removed from mac80211 and should be moved to the driver. I'm > thinking of this, because rt2x00 is not the only one having problems and > Felix comment in > http://news.gmane.org/find-root.php?group=gmane.linux.drivers.rt2x00.user&article=1383 > > "If you want to tear down the BA session in rt2x00, either do it in the > driver or add a proper flag to ensure that ath9k remains unaffected by > the change." > > sounds to me really ath9k specific (what about other hardware)? The commit f0425beda is aimed not specifically at Atheros hardware. It is meant for any hardware that lets the driver track the Tx BA window and has a reasonable MAC design. The 'reasonable MAC design' part is where rt2x00 falls short. BAR Tx status processing is just one of several places where the hardware interface design is stupid and limiting, meaning the driver has to do extra effort to work around that. - Felix -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
