On 02/06/2014 08:23 AM, Sujith Manoharan wrote: > Ben Greear wrote: >> Can you let us know the details on how your set up that TCP >> traffic? For instance, number of streams, write size, socket >> buffer sizes, etc? Upload, download, or are both similar >> throughput in your testing? > > Stock OpenWrt (trunk) running on a 3x3 Scorpion board (AP136/AP135) as AP. > Windows 7 as client, using a 3x3 AR9300 card. > > iperf with window size 512k, 4 parallel threads. With both > TX and RX, 290+ Mbps is seen. UDP traffic: 330 Mbps in both directions. > Environment: open air and the station is located about 1 meter from the AP. We get similar UDP throughput (and maybe up to 340Mbps using ath9k rate control), but not so good on TCP. All our tests so far are on 3.9 kernel, so maybe things are better on later kernels. Someday soon-ish we'll be moving to newer kernels and will test it again. >> I find that those settings influence throughput a great deal, >> and I have not yet been able to reach 295Mbps of TCP throughput >> in our testing w/out hacking the tcp-ack logic to increase ack delays. > > By adjusting TCP parameters using sysctl or hacking the code ? There is no sysctl for this in upstream code as far as I know ...I ended up hacking code by modifying some delayed-ack patches someone else posted some time back. Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- 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
