Date: Mon, 31 Oct 2011 12:12:10 +1100 From: Adrian Chadd <adrian@freebsd.org> To: Lev Serebryakov <lev@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: AR9280: very strange upload speed Message-ID: <CAJ-VmonmaZqT=oorUhi0qZJRxnJ9oDEVeY5gYU2c5TiinUwH4g@mail.gmail.com> In-Reply-To: <591784976.20111030232455@serebryakov.spb.ru> References: <872994138.20111026222719@serebryakov.spb.ru> <CAJ-Vmonbsq35Jc=H_G%2BZKgVH1DvNSPkSKoJMLVG1vx7OcHdNaw@mail.gmail.com> <723076644.20111030221555@serebryakov.spb.ru> <591784976.20111030232455@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Please do this: * sysctl dev.ath.0.sample_stats then past the dmesg output here, so I can see what kind of TX failures you're seeing. * UDP iperf only gives useful stats on the RX side, so you have to do this: + RX side: iperf -su -i 1 + TX side: iperf -c x.x.x.x -u -b 100m -i 5 -t 10 (just so you see it running) + watch the RX side Do that in both directions, see which direction works better. TCP is difficult as the throughput depends upon both TX/RX behaviour. I expect that the TX side is great, the RX side sucks, and you're getting lots of stuck beacons. Try my patch from another email thread and see if that helps things. Finally, try changing channels. I had some very strange behaviour where some channels would work great and some wouldn't. I really need to find someone to sit down and finish the channel usage code. :( adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonmaZqT=oorUhi0qZJRxnJ9oDEVeY5gYU2c5TiinUwH4g>