diff options
author | Sujith Manoharan <c_manoha@qca.qualcomm.com> | 2014-02-06 10:22:55 +0530 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2014-02-12 15:36:04 -0500 |
commit | 9e495a2603334f9c8fcc6802300c22fc8a0eae02 (patch) | |
tree | e26922f0ccd4fb01bcaad53500f69977494e4fdc /fs | |
parent | 482b30b653e2be8aa1bf70b7aaac56ff0aeb070c (diff) | |
download | linux-9e495a2603334f9c8fcc6802300c22fc8a0eae02.tar.gz linux-9e495a2603334f9c8fcc6802300c22fc8a0eae02.tar.bz2 linux-9e495a2603334f9c8fcc6802300c22fc8a0eae02.zip |
ath9k: Remove ath9k rate control
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: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions