Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Stephen Donecker <sdonecker@ahmct.ucdavis.edu>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Low throughput AR9280 HT40+
Date: Tue, 12 Jun 2012 18:58:51 -0700	[thread overview]
Message-ID: <4FD7F3DB.4020102@ahmct.ucdavis.edu> (raw)

Hi,

I appear to be getting lower throughput than I should be between two 
single stream adhoc nodes (~78Mbps UDP). Shouldn't I be getting closer 
to ~128Mbps? Could someone explain why such a high ratio of lost 
datagrams? When looking through the list the vast majority of people get 
a very small datagram loss.

Hardware:
Ubiquity Routerstation (AR7161)
Ubiquity SR71-15 (AR9280)
OpenWRT r32062 (linux-3.3.8, compat-wireless-2012-05-29)

Config:
# cat /sys/kernel/debug/ieee80211/phy0/frequency
5785
# cat /sys/kernel/debug/ieee80211/phy0/channel_type
ht40+
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/tx_chainmask
0x00000001
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask
0x00000001

Throughput test:
# iperf -c 192.168.11.2 -p 7777 -u -b 150m -t 10 -i 1
------------------------------------------------------------
Client connecting to 192.168.11.2, UDP port 7777
Sending 1470 byte datagrams
UDP buffer size:  160 KByte (default)
------------------------------------------------------------
[  3] local 192.168.11.1 port 47537 connected with 192.168.11.2 port 7777
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  15.3 MBytes   128 Mbits/sec
[  3]  1.0- 2.0 sec  15.1 MBytes   126 Mbits/sec
[  3]  2.0- 3.0 sec  15.3 MBytes   128 Mbits/sec
[  3]  3.0- 4.0 sec  15.3 MBytes   128 Mbits/sec
[  3]  4.0- 5.0 sec  15.4 MBytes   129 Mbits/sec
[  3]  5.0- 6.0 sec  15.3 MBytes   129 Mbits/sec
[  3]  6.0- 7.0 sec  15.3 MBytes   128 Mbits/sec
[  3]  7.0- 8.0 sec  15.2 MBytes   128 Mbits/sec
[  3]  8.0- 9.0 sec  15.3 MBytes   128 Mbits/sec
[  3]  0.0-10.0 sec   153 MBytes   128 Mbits/sec
[  3] Sent 108972 datagrams
[  3] Server Report:
[  3]  0.0-10.0 sec  92.9 MBytes  77.8 Mbits/sec   0.243 ms 42715/108973 
(39%)

# iw dev wlan0 station dump
Station 00:15:6d:85:0f:78 (on wlan0)
     inactive time:    170 ms
     rx bytes:    102078921
     rx packets:    85286
     tx bytes:    1412173463
     tx packets:    921845
     tx retries:    209
     tx failed:    0
     signal:      -56 [-56] dBm
     signal avg:    -55 [-55] dBm
     tx bitrate:    150.0 MBit/s MCS 7 40Mhz short GI
     rx bitrate:    150.0 MBit/s MCS 7 40Mhz short GI
     authorized:    yes
     authenticated:    yes
     preamble:    long
     WMM/WME:    yes
     MFP:        no
     TDLS peer:    no

Thanks,

-Stephen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120612/74d1449d/attachment-0001.htm 

                 reply	other threads:[~2012-06-13  1:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FD7F3DB.4020102@ahmct.ucdavis.edu \
    --to=sdonecker@ahmct.ucdavis.edu \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox