From: Nenad Opsenica <nenad@panline.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k bad performances
Date: Thu, 05 Nov 2009 21:47:36 +0100 [thread overview]
Message-ID: <4AF339E8.4060708@panline.net> (raw)
In-Reply-To: <40101cc30911051037r793bd0a8re3447cea115534d@mail.gmail.com>
Matteo,
Try to turn off power savings feature on STA:
iwconfig wlan0 power off
What performance could you get after that?
Regards,
Nenad
Matteo Croce wrote:
> Hi.
>
> i'm playing with ath9k and I get very poor performances. I noticed
> that I can send data fast to the AP but the AP is very slow to send,
> both devices are running openwrt trunk with latest ath9k from linville's tree.
> The card are Ubiquiti SR71-A MIMO 3x3 with and AR9160 chipset in it.
> The devices are close enough (not too much) and noone else is
> transmitting on the 5 GHz band
> here are some informations that could help:
>
> # client -> AP
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 0.0- 1.0 sec 7.58 MBytes 63.6 Mbits/sec 0.171 ms 490/ 5896 (8.3%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 1.0- 2.0 sec 7.78 MBytes 65.3 Mbits/sec 0.240 ms 379/ 5932 (6.4%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 2.0- 3.0 sec 7.71 MBytes 64.7 Mbits/sec 0.158 ms 436/ 5937 (7.3%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 3.0- 4.0 sec 7.48 MBytes 62.8 Mbits/sec 0.432 ms 593/ 5931 (10%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 4.0- 5.0 sec 7.39 MBytes 62.0 Mbits/sec 0.194 ms 258/ 5526 (4.7%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 5.0- 6.0 sec 7.08 MBytes 59.4 Mbits/sec 0.214 ms 605/ 5658 (11%)
>
> # AP -> client
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 0.0- 1.0 sec 574 KBytes 4.70 Mbits/sec 8.346 ms 108/ 508 (21%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 1.0- 2.0 sec 546 KBytes 4.47 Mbits/sec 0.877 ms 54/ 434 (12%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 2.0- 3.0 sec 894 KBytes 7.33 Mbits/sec 6.866 ms 48/ 671 (7.2%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 3.0- 4.0 sec 309 KBytes 2.53 Mbits/sec 1.564 ms 61/ 276 (22%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 4.0- 5.0 sec 702 KBytes 5.75 Mbits/sec 3.300 ms 27/ 516 (5.2%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 5.0- 6.0 sec 314 KBytes 2.58 Mbits/sec 8.627 ms 59/ 278 (21%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 6.0- 7.0 sec 296 KBytes 2.42 Mbits/sec 18.781 ms 25/ 231 (11%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 7.0- 8.0 sec 993 KBytes 8.14 Mbits/sec 2.878 ms 80/ 772 (10%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 8.0- 9.0 sec 706 KBytes 5.79 Mbits/sec 6.422 ms 58/ 550 (11%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 9.0-10.0 sec 334 KBytes 2.74 Mbits/sec 4.557 ms 42/ 275 (15%)
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
> [ 3] 0.0-10.9 sec 5.57 MBytes 4.30 Mbits/sec 91.782 ms 568/ 4543 (13%)
>
> # ping 10.0.0.1 # client -> AP
> PING 10.0.0.1 (10.0.0.1): 56 data bytes
> 64 bytes from 10.0.0.1: seq=0 ttl=64 time=2.762 ms
> 64 bytes from 10.0.0.1: seq=1 ttl=64 time=3.866 ms
> 64 bytes from 10.0.0.1: seq=2 ttl=64 time=2.613 ms
> 64 bytes from 10.0.0.1: seq=3 ttl=64 time=2.777 ms
> ^C
> --- 10.0.0.1 ping statistics ---
> 4 packets transmitted, 4 packets received, 0% packet loss
> round-trip min/avg/max = 2.613/3.004/3.866 ms
> # ping 10.0.0.2 # AP -> client
> PING 10.0.0.2 (10.0.0.2): 56 data bytes
> 64 bytes from 10.0.0.2: seq=0 ttl=64 time=146.080 ms
> 64 bytes from 10.0.0.2: seq=1 ttl=64 time=55.668 ms
> 64 bytes from 10.0.0.2: seq=2 ttl=64 time=78.811 ms
> 64 bytes from 10.0.0.2: seq=3 ttl=64 time=102.908 ms
> 64 bytes from 10.0.0.2: seq=4 ttl=64 time=25.216 ms
> ^C
> --- 10.0.0.2 ping statistics ---
> 5 packets transmitted, 5 packets received, 0% packet loss
> round-trip min/avg/max = 25.216/81.736/146.080 ms
>
> # while sleep 1 ; do iw dev wlan0 link; done
> Connected to 00:15:6d:84:13:06 (on wlan0)
> SSID: OpenWrt
> freq: 5180
> RX: 279472 bytes (1931 packets)
> TX: 822486078 bytes (536976 packets)
> signal: -18 dBm
> tx bitrate: 324.0 MBit/s MCS 28 40Mhz
> Connected to 00:15:6d:84:13:06 (on wlan0)
> SSID: OpenWrt
> freq: 5180
> RX: 211507 bytes (1450 packets)
> TX: 423926440 bytes (276793 packets)
> signal: -18 dBm
> tx bitrate: MCS 36 40Mhz
> Connected to 00:15:6d:84:13:06 (on wlan0)
> SSID: OpenWrt
> freq: 5180
> RX: 275354 bytes (1902 packets)
> TX: 797028834 bytes (520359 packets)
> signal: -18 dBm
> tx bitrate: 324.0 MBit/s MCS 28 40Mhz
> Connected to 00:15:6d:84:13:06 (on wlan0)
> SSID: OpenWrt
> freq: 5180
> RX: 276632 bytes (1911 packets)
> TX: 806084486 bytes (526270 packets)
> signal: -18 dBm
> tx bitrate: 324.0 MBit/s MCS 28 40Mhz
>
>
> # cat /etc/hostapd.conf
> driver=nl80211
> interface=wlan0
> hw_mode=a
>
>
> ssid=OpenWrt
> wpa=0
>
> country_code=US
> channel=36
> ieee80211n=1
> ht_capab=[SHORT-GI-40][HT40+]
>
>
>
> wme_enabled=1
> wme_ac_bk_cwmin=4
> wme_ac_bk_cwmax=10
> wme_ac_bk_aifs=7
> wme_ac_bk_txop_limit=0
> wme_ac_bk_acm=0
> wme_ac_be_aifs=3
> wme_ac_be_cwmin=4
> wme_ac_be_cwmax=10
> wme_ac_be_txop_limit=0
> wme_ac_be_acm=0
> wme_ac_vi_aifs=2
> wme_ac_vi_cwmin=3
> wme_ac_vi_cwmax=4
> wme_ac_vi_txop_limit=94
> wme_ac_vi_acm=0
> wme_ac_vo_aifs=2
> wme_ac_vo_cwmin=2
> wme_ac_vo_cwmax=3
> wme_ac_vo_txop_limit=47
> wme_ac_vo_acm=0
> tx_queue_data3_aifs=7
> tx_queue_data3_cwmin=15
> tx_queue_data3_cwmax=1023
> tx_queue_data3_burst=0
> tx_queue_data2_aifs=3
> tx_queue_data2_cwmin=15
> tx_queue_data2_cwmax=63
> tx_queue_data2_burst=0
> tx_queue_data1_aifs=1
> tx_queue_data1_cwmin=7
> tx_queue_data1_cwmax=15
> tx_queue_data1_burst=3.0
> tx_queue_data0_aifs=1
> tx_queue_data0_cwmin=3
> tx_queue_data0_cwmax=7
> tx_queue_data0_burst=1.5
>
> # dmesg
> cfg80211: Calling CRDA to update world regulatory domain
> cfg80211: World regulatory domain updated:
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> PCI: Enabling device 0000:00:11.0 (0000 -> 0002)
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> Registered led device: ath9k-phy0::radio
> Registered led device: ath9k-phy0::assoc
> Registered led device: ath9k-phy0::tx
> Registered led device: ath9k-phy0::rx
> phy0: Atheros AR9160 MAC/BB Rev:0 AR5133 RF Rev:b0 mem=0xb0000000, irq=48
> # hostapd -v
> hostapd v0.6.9
> User space daemon for IEEE 802.11 AP management,
> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
> Copyright (c) 2002-2009, Jouni Malinen <j@w1.fi> and contributors
>
>
>
> Cheers,
> Matteo Croce
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
next prev parent reply other threads:[~2009-11-05 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 18:37 [ath9k-devel] ath9k bad performances Matteo Croce
2009-11-05 20:47 ` Nenad Opsenica [this message]
2009-11-06 1:43 ` xxiao
2009-11-07 22:28 ` [ath9k-devel] [Bulk] " rootkit85 at yahoo.it
2009-11-07 22:42 ` rootkit85 at yahoo.it
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=4AF339E8.4060708@panline.net \
--to=nenad@panline.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.