From: Glenn Burkhardt <gbburkhardt@verizon.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: Nick Kossifidis <mickflemm@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: poor performance with ath5k; reverting to ath_pci
Date: Wed, 21 Jan 2009 21:58:13 -0500 [thread overview]
Message-ID: <200901212158.13854.gbburkhardt@verizon.net> (raw)
In-Reply-To: <b6c5339f0901160733u433b1154sfb8b5662c4fe991c@mail.gmail.com>
On Friday 16 January 2009 10:33:13 Bob Copeland wrote:
> On Thu, Jan 15, 2009 at 5:34 PM, Glenn Burkhardt
>
> <gbburkhardt@verizon.net> wrote:
> > ath5k_pci 0000:00:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> > ath5k_pci 0000:00:07.0: registered as 'phy0'
> > phy0: Selected rate control algorithm 'pid'
>
> Can you change the rate control algorithm to minstrel and retry?
I'll have to say that performance is worse with minstrel than pid rate
control. I used Channel 2 on the router, and:
ath_pci:
DepotRd:/home/gbb-suse/wireless # ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=5.82 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.32 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.967 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.954 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.970 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=1.14 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=1.32 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.981 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=0.961 ms
64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.88 ms
64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.962 ms
64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=0.894 ms
64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=0.991 ms
64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=0.968 ms
64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=0.978 ms
64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.10 ms
64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=0.999 ms
64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=0.998 ms
DepotRd:/home/gbb-suse/wireless # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"Belkin_N_Wireless_A99331"
Mode:Managed Frequency:2.417 GHz Access Point: 00:1C:DF:A9:93:31
Bit Rate:36 Mb/s Tx-Power:15 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:FA2D-087E-61EF-D860-2E7D-46C9-AF65-CA4C Security
mode:restricted
Power Management:off
Link Quality=37/70 Signal level=-59 dBm Noise level=-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ath5k with pid:
DepotRd:/home/gbb-suse/linux-2.6.28.1 # ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1729 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=2320 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=2050 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=1402 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=1323 ms
64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=1151 ms
64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=608 ms
64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=1134 ms
64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=1100 ms
64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=356 ms
64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=164 ms
64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=423 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=407 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=1086 ms
64 bytes from 192.168.2.1: icmp_seq=24 ttl=64 time=1442 ms
DepotRd:~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"Belkin_N_Wireless_A99331"
Mode:Managed Frequency:2.417 GHz Access Point: 00:1C:DF:A9:93:31
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:E854-5075-1208-1225-D46B-46E6-CB2C-B627-DA3D-788E-
F50E-7351-DDE0-C111-E9A5-1FB7 [2] Security mode:open
Power Management:off
Link Quality=53/100 Signal level:-69 dBm Noise level=-103 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ath5k with minstrel
dmesg | egrep 'ath|phy'
BIOS-provided physical RAM map:
Setting physnode_map array to node 0 for pfns:
ath5k_pci 0000:00:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ath5k_pci 0000:00:07.0: registered as 'phy0'
phy0: Selected rate control algorithm 'minstrel'
ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
ath5k phy0: RF2112B 2GHz radio found (0x46)
DepotRd:# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=13159 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=40968 ms
64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=42986 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=41983 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=42860 ms
DepotRd:~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"Belkin_N_Wireless_A99331"
Mode:Managed Frequency:2.417 GHz Access Point: 00:1C:DF:A9:93:31
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:1193-9C46-9CB0-B2EE-99CA-EA37-7EB4-1B62-9475-B834-
AE70-AA4F-B4A5-B303-3D51-4244 [2] Security mode:open
Power Management:off
Link Quality=56/100 Signal level:-67 dBm Noise level=-103 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
next prev parent reply other threads:[~2009-01-23 1:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 5:03 poor performance with ath5k; reverting to ath_pci Glenn Burkhardt
2009-01-14 13:30 ` Nick Kossifidis
2009-01-15 22:34 ` Glenn Burkhardt
2009-01-16 15:33 ` Bob Copeland
2009-01-21 3:38 ` Glenn Burkhardt
2009-01-21 15:14 ` John W. Linville
2009-01-21 18:22 ` Stefanik Gábor
2009-01-21 19:11 ` John W. Linville
2009-01-21 19:33 ` Stefanik Gábor
2009-01-21 19:34 ` John W. Linville
2009-01-22 4:32 ` Nick Kossifidis
2009-01-22 13:49 ` John W. Linville
2009-01-22 14:04 ` Johannes Berg
2009-01-22 14:17 ` John W. Linville
2009-01-22 14:45 ` Stefanik Gábor
2009-01-22 15:18 ` John W. Linville
2009-01-22 2:58 ` Glenn Burkhardt [this message]
2009-01-23 7:31 ` Nick Kossifidis
2009-02-03 2:36 ` Glenn Burkhardt
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=200901212158.13854.gbburkhardt@verizon.net \
--to=gbburkhardt@verizon.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).