1. 29 8月, 2014 2 次提交
  2. 19 7月, 2014 1 次提交
    • F
      ath9k: fix pending tx frames accounting · d954cd77
      Felix Fietkau 提交于
      Packets originally buffered for the regular hardware tx queues can end
      up being transmitted through the U-APSD queue (via PS-Poll or U-APSD).
      When packets are dropped due to retransmit failures, the pending frames
      counter is not always updated properly.
      Fix this by keeping track of the queue that a frame was accounted for in
      the ath_frame_info struct, and using that on completion to decide
      whether the counter should be updated.
      This fixes some spurious transmit queue hangs.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      d954cd77
  3. 20 6月, 2014 24 次提交
  4. 30 5月, 2014 1 次提交
  5. 23 5月, 2014 1 次提交
  6. 14 5月, 2014 1 次提交
  7. 30 4月, 2014 1 次提交
    • F
      ath9k: remove tid->paused flag · 62e54dbb
      Felix Fietkau 提交于
      There are some corner cases where the driver could get stuck with a full
      tid queue that is paused, leading to a software tx queue hang.
      
      Since the tx queueing rework, pausing per-tid queues on aggregation
      session setup is no longer necessary. The driver will assign sequence
      numbers to buffered frames when a new session is established, in order
      to get the correct starting sequence number.
      
      mac80211 prevents new frames from entering the queue during setup.
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      62e54dbb
  8. 23 4月, 2014 1 次提交
  9. 18 3月, 2014 5 次提交
  10. 01 3月, 2014 2 次提交
  11. 13 2月, 2014 1 次提交
    • S
      ath9k: Remove ath9k rate control · 9e495a26
      Sujith Manoharan 提交于
      There is no benefit in retaining the legacy rate control module
      in the driver codebase.
      
      It is known to be buggy and has less than optimal performance
      in real-world environments compared with minstrel. The only
      reason that it was kept when we made the switch to minstrel
      as default was that it showed higher throughput numbers in a
      clean/ideal environment.
      
      This is no longer the case and minstrel can push ath9k to
      the same throughput levels. In TCP, with 3-stream cards, more than
      295 Mbps can be obtained in open air, with 2-stream cards,
      210 Mbps is easily reached. To test performance issues,
      instead of using a broken rate control module, it is better
      to use the fixed-rate interface provided by mac80211 anyway.
      
      The ath9k RC has not received any bug fixes in years and is
      just bit-rotting away - this patch removes it.
      Signed-off-by: NSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      9e495a26