From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Tue, 26 Aug 2008 16:01:32 -0700 Subject: [ath9k-devel] Poor performance on AR5418 In-Reply-To: <14d615330808261547l5ea24ffcs4dd7234133ea1cfd@mail.gmail.com> References: <14d615330808261509rf0130e1h5c092e7846b29bbc@mail.gmail.com> <43e72e890808261523ud3f82d6gaaf944df670d80d3@mail.gmail.com> <14d615330808261547l5ea24ffcs4dd7234133ea1cfd@mail.gmail.com> Message-ID: <20080826230132.GE9211@tesla> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Tue, Aug 26, 2008 at 03:47:05PM -0700, Jeremy Apthorp wrote: > 2008/8/27 Luis R. Rodriguez : > > On Tue, Aug 26, 2008 at 3:09 PM, Jeremy Apthorp 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