From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] weird low throughput avg. 42Mbps && high CPU load as a SU
Date: Wed, 03 Feb 2010 23:18:03 +0100 [thread overview]
Message-ID: <4B69F61B.3020000@openwrt.org> (raw)
In-Reply-To: <8CC72C442B48AB8-5404-73F1@webmail-d059.sysops.aol.com>
On 2010-02-03 9:44 AM, oiioeu at aol.com wrote:
>
> I use IXP425( CPU 533M, 64M RAM ) platform, OpenWrt r18530 with
> compat-wireless-2009-11-21.
> As an AP, it worked just good I could see an average throughput like
> 70~80Mbps under HT40( the throughput limited by the 100M ethernet in my
> test environment).
>
> As a SU, I tested with a compex wp543 AP and got a throughput like
> 42~45Mbps under HT40( I think the AP uses HT20 ) so the iw wlan0 station
> dump on SU shows:
OpenWrt r18530 is very old. A lot of things that can affect wifi
performance have changed since that revision. I would recommend building
a current version of OpenWrt and rerunning your tests with it.
- Felix
next prev parent reply other threads:[~2010-02-03 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 8:44 [ath9k-devel] weird low throughput avg. 42Mbps && high CPU load as a SU oiioeu at aol.com
2010-02-03 22:18 ` Felix Fietkau [this message]
2010-02-04 5:06 ` oiioeu at aol.com
2010-02-04 5:49 ` oiioeu at aol.com
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=4B69F61B.3020000@openwrt.org \
--to=nbd@openwrt.org \
--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.