From: Larry Finger <Larry.Finger@lwfinger.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "Cédric Auger" <cedric@grisbi.org>, linux-wireless@vger.kernel.org
Subject: Re: iwl3945 slow for downloading
Date: Sat, 26 Jul 2008 10:54:41 -0500 [thread overview]
Message-ID: <488B48C1.6090506@lwfinger.net> (raw)
In-Reply-To: <488B3969.4050405@openwrt.org>
Felix Fietkau wrote:
> I don't know if it helps with debugging this issue, but I've seen the same
> on a laptop from a friend of mine (same card).
>
> After some searching I found that setting the AP to g-only mode instead of
> b+g mixed made it work at decent speeds. Another symptom of this slowdown is
> that there is typically an unnaturally high number of retransmissions on the
> air, which eats up a lot of airtime.
>
> I've spent some time looking through the code to find the reason for this
> but couldn't find anything yet (maybe somebody from Intel could help).
Just for comparison, my BCM4312 running b43 from the latest wireless-testing
gets the following tcpperf throughput:
AP Mode TX RX
Mixed b/g 19.8 MB/s 23.0 MB/s
g-only 20.5 MB/s 23.1 MB/s
For these tests, the connecting end was wired to the router. The difference in
TX speeds was about what I expected - the small difference in RX speeds was not.
In any case, if you see a large difference with iwl3945, that would be useful
information.
You can obtain tcpperf from http://wand.cs.waikato.ac.nz/~stj2/nsc/software.html
Larry
next prev parent reply other threads:[~2008-07-26 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 14:11 iwl3945 slow for downloading Cédric Auger
2008-07-26 14:49 ` Felix Fietkau
2008-07-26 15:54 ` Larry Finger [this message]
2008-07-26 16:32 ` Cédric Auger
2008-07-26 21:10 ` Larry Finger
2008-07-27 6:30 ` Cédric Auger
2008-07-27 14:33 ` Stefan Monnier
2008-07-27 14:48 ` Larry Finger
2008-07-26 16:56 ` Felix Fietkau
2008-07-27 6:40 ` Cédric Auger
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=488B48C1.6090506@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=cedric@grisbi.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).