From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Poor performance on AR5418
Date: Tue, 26 Aug 2008 16:01:32 -0700 [thread overview]
Message-ID: <20080826230132.GE9211@tesla> (raw)
In-Reply-To: <14d615330808261547l5ea24ffcs4dd7234133ea1cfd@mail.gmail.com>
On Tue, Aug 26, 2008 at 03:47:05PM -0700, Jeremy Apthorp wrote:
> 2008/8/27 Luis R. Rodriguez <mcgrof@gmail.com>:
> > On Tue, Aug 26, 2008 at 3:09 PM, Jeremy Apthorp <nornagon@gmail.com> wrote:
> >> I just built and tested out kernel 2.6.27-rc4 (with ath9k drivers
> >> included) on my MacBook Pro 3,1. There's good news and there's bad
> >> news.
> >>
> >> The good news is that the AR5418 is discovered and added as a device,
> >> and it works! It associates and I can ping places.
> >>
> >> The bad news is that it's really, really slow. iwconfig reported a
> >> network speed of 1Mbps, vs. the 24Mbps+ that I get from madwifi (this
> >> is a g network). Link quality seems normal; it hangs around 15-30/100
> >> compared to around 20/70 under madwifi. However, I get 65%+ packet
> >> loss just pinging my router from ath9k, and zero from madwifi.
> >>
> >> Is anyone else having this problem? Is there anything I can do to help
> >> it get fixed? Unfortunately I don't have any experience with wifi
> >> drivers, so I'd not be much use for code... but I can run tests and
> >> collect debug info if necessary.
> >
> > Link quality is not 100% correct, its actually better. We need to add
> > noise floor calibration to get it to report more accurate values. So
> > for now just use it as a guide. Also the rate reported by iwconfig is
> > not correct, please rely on iperf for proper performance tests.
>
> I was more concerned about the packet loss than the link quality or
> the reported rate. Also, I tried loading google.com in a browser, and
> it took several minutes.
How soon after associating and getting an IP and pinging do you get
packet loss? Whatever it is we definitely will need to fix it.
Luis
next prev parent reply other threads:[~2008-08-26 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 22:09 [ath9k-devel] Poor performance on AR5418 Jeremy Apthorp
2008-08-26 22:23 ` Luis R. Rodriguez
2008-08-26 22:47 ` Jeremy Apthorp
2008-08-26 23:01 ` Luis R. Rodriguez [this message]
2008-08-26 23:02 ` Jeremy Apthorp
2008-08-27 6:11 ` sHittmeyer
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 22:49 Amit Sood
2008-08-26 23:53 Amit Sood
2008-08-27 1:33 ` John Dong
2008-08-27 8:44 Amit Sood
2008-08-27 11:08 ` F
2008-08-27 14:59 Amit Sood
2008-08-27 17:22 ` Luis R. Rodriguez
2008-08-27 23:10 ` John Dong
2008-08-28 0:48 ` F
2008-08-28 6:26 Amit Sood
2008-08-29 10:03 Amit Sood
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=20080826230132.GE9211@tesla \
--to=lrodriguez@atheros.com \
--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.