From: Florian Fainelli <florian@openwrt.org>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
users@rt2x00.serialmonkey.com,
Helmut Schaa <helmut.schaa@googlemail.com>,
gwingerde@gmail.com, ivdoorn@gmail.com
Subject: Poor RT2880 performance
Date: Mon, 13 Feb 2012 14:23:31 +0100 [thread overview]
Message-ID: <4F390ED3.8010400@openwrt.org> (raw)
Hello,
I am playing with a RT2880-F based AP, with a N connected station, in a
residential environment.
I could not get more than 26Mbits/sec TCP performance using iperf on
both sides, changing to a busier channel even made the performance drop
down to 5Mbits/sec, and remained like this.
Let me know if you need more informations like survey dumps etc ... it
does not seem like we are hitting the CPU bounds here, I can also attach
the EEPROM in case it helps.
Thank you very much.
--
Florian
next reply other threads:[~2012-02-13 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:23 Florian Fainelli [this message]
2012-02-13 13:45 ` Poor RT2880 performance Helmut Schaa
2012-02-13 15:05 ` Andreas Hartmann
2012-02-13 19:18 ` Florian Fainelli
2012-02-16 13:00 ` Stanislaw Gruszka
2012-02-17 8:50 ` Florian Fainelli
2012-02-17 8:52 ` Helmut Schaa
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=4F390ED3.8010400@openwrt.org \
--to=florian@openwrt.org \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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 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.