aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic/pending-4.9
diff options
context:
space:
mode:
authorKoen Vandeputte <koen.vandeputte@ncentric.com>2018-11-05 11:31:12 +0100
committerKoen Vandeputte <koen.vandeputte@ncentric.com>2018-11-06 11:49:55 +0100
commit779b89c7577de4d7615e2975341fc8ffc580ca09 (patch)
tree425efd9e54be2e1a007176dc9ca7d7741fe95fe1 /target/linux/generic/pending-4.9
parentf9c79947b5c4e726ecf5afd1b04d99f0b4101755 (diff)
downloadupstream-779b89c7577de4d7615e2975341fc8ffc580ca09.tar.gz
upstream-779b89c7577de4d7615e2975341fc8ffc580ca09.tar.bz2
upstream-779b89c7577de4d7615e2975341fc8ffc580ca09.zip
ath9k: fix dynack in IBSS mode
Currently, dynack was only tested upstream using AP/STA mode. Testing it on IBSS, showed that late-ack detection was broken. This is caused due to dynack using Association Request/Response frames for late-ack detection, which IBSS does not use. Also allowing Authentication frames here solves this. A second issue also got fixed, which was also seen AP/STA mode: When a station was added, the estimated value would be exponentially averaged using 0 as a starting point. This means that on larger distances, the ack timeout was still not high enough before synchronizing would run out of late-ack's for estimation. Fix this by using the initial estimated value as a baseline and only start averaging in the following estimation rounds. Test setup: - 2x identical devices: RB912UAG-5HPnD + 19dB sector - IBSS - 2x2 802.11an (ar9340), HT20, long GI - RSSI's -70 / -71 - Real distance: 23910 meter Results (60s iperf runs): Fixed coverage class 54 (up to 24300m): * 21.5 Mbits/sec Dynack: * 28.9 Mbits/sec Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
Diffstat (limited to 'target/linux/generic/pending-4.9')
0 files changed, 0 insertions, 0 deletions