My test is very simple. Continuous ping at about 10 ping per node per second. Ping size 64 bytes -----Original Message----- From: Paul Stoaks [mailto:paul@xxxxxxxxxxxxxxxxxxx] Sent: Monday, December 03, 2012 1:22 PM To: 'Georgiewskiy Yuriy'; Chaoxing Lin Cc: linux-wireless@xxxxxxxxxxxxxxx Subject: RE: help: 802.11s bad performance with 802.11n enabled What kind of traffic are you pushing through (packet sizes?) Are they fixed size, fixed rate, or ...? Paul -----Original Message----- From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless-owner@xxxxxxxxxxxxxxx] On Behalf Of Georgiewskiy Yuriy Sent: Monday, December 03, 2012 7:44 AM To: Chaoxing Lin Cc: linux-wireless@xxxxxxxxxxxxxxx Subject: RE: help: 802.11s bad performance with 802.11n enabled On 2012-12-03 14:56 -0000, Chaoxing Lin wrote Georgiewskiy Yuriy: CL>CL>For experiment, I changed ath9k driver to disable 802.11n packet aggregation. The network becomes much better. CL>CL>It's as stable as running 802.11a only mode. CL>CL>So it seems that the aggregation plays a big role in in-stability CL>CL>of 802.11s network with 802.11n. CL>CL>Any one has any idea why? CL> CL>Can you post a patch? i want test this too. CL> CL>The change is easy CL>In ath9k/init.c CL>Function ath9k_set_hw_capab() CL>Replace below CL> if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT) CL> hw->flags |= IEEE80211_HW_AMPDU_AGGREGATION; with CL> hw->flags &= ~IEEE80211_HW_AMPDU_AGGREGATION; On first look in my case disabled aggregation reduces packet loss, link is more reliable, but it's also drop throughput to 15-20 Mbits/sec from about ~50 with aggregation enabled. C уважением With Best Regards Георгиевский Юрий. Georgiewskiy Yuriy +7 4872 711666 +7 4872 711666 факс +7 4872 711143 fax +7 4872 711143 Компания ООО "Ай Ти Сервис" IT Service Ltd http://nkoort.ru http://nkoort.ru JID: GHhost@xxxxxxxxxx JID: GHhost@xxxxxxxxxx YG129-RIPE YG129-RIPE -- 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
