From: Stanislaw Gruszka <sgruszka@redhat.com>
To: poma <pomidorabelisima@gmail.com>
Cc: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: [rt2x00-users] Ralink RT3070(rt2800usb) - The Tortoise and the Hare
Date: Sun, 2 Nov 2014 14:00:10 +0100 [thread overview]
Message-ID: <20141102130003.GA10104@redhat.com> (raw)
In-Reply-To: <5455C833.2080706@gmail.com>
On Sun, Nov 02, 2014 at 06:59:15AM +0100, poma wrote:
> Higher values, are they even possible via rt2800usb.ko & Co.?
Yes.
> ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
> ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
On the same RT and RF chipsets with TP-link WR-1043ND access point I have:
# iperf -c 192.168.1.105 -i 1
------------------------------------------------------------
Client connecting to 192.168.1.105, TCP port 5001
TCP window size: 45.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.100 port 56993 connected with 192.168.1.105 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 4.75 MBytes 39.8 Mbits/sec
[ 3] 1.0- 2.0 sec 8.12 MBytes 68.2 Mbits/sec
[ 3] 2.0- 3.0 sec 8.00 MBytes 67.1 Mbits/sec
[ 3] 3.0- 4.0 sec 8.75 MBytes 73.4 Mbits/sec
[ 3] 4.0- 5.0 sec 7.00 MBytes 58.7 Mbits/sec
[ 3] 5.0- 6.0 sec 9.00 MBytes 75.5 Mbits/sec
[ 3] 6.0- 7.0 sec 8.25 MBytes 69.2 Mbits/sec
[ 3] 7.0- 8.0 sec 7.75 MBytes 65.0 Mbits/sec
[ 3] 8.0- 9.0 sec 8.75 MBytes 73.4 Mbits/sec
[ 3] 9.0-10.0 sec 7.75 MBytes 65.0 Mbits/sec
[ 3] 0.0-10.0 sec 78.2 MBytes 65.5 Mbits/sec
Stanislaw
next prev parent reply other threads:[~2014-11-02 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 5:59 Ralink RT3070(rt2800usb) - The Tortoise and the Hare poma
2014-11-02 13:00 ` Stanislaw Gruszka [this message]
2014-11-02 15:23 ` [rt2x00-users] " poma
2014-11-02 21:52 ` poma
2014-11-03 7:34 ` poma
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=20141102130003.GA10104@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--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 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).