linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Josef Semler <josef.semler@gmail.com>
Cc: Sujith Manoharan <c_manoha@qca.qualcomm.com>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] Anyone doing WiFi throughput tests?
Date: Sat, 26 May 2012 14:35:55 +0200	[thread overview]
Message-ID: <4FC0CE2B.9060005@openwrt.org> (raw)
In-Reply-To: <CAPsaeQPxh0Yd+GT3HbReAAtoPhKF2c3kOzgOPL6xK7NC=8J4qA@mail.gmail.com>

On 2012-05-26 9:55 AM, Josef Semler wrote:
> 
> 
> 2012/5/26 Sujith Manoharan <c_manoha@qca.qualcomm.com
> <mailto:c_manoha@qca.qualcomm.com>>
> 
>     Joe Semler wrote:
>     > > With a XB112 card (3x3) in HT40 mode, 5Ghz, TX throughput (TCP)
>     can reach 290 Mbps.
>     > > Sample iperf run:
>     > >
>     > > [  3] 28.0-29.0 sec  34.1 MBytes   286 Mbits/sec
>     > > [  3] 29.0-30.0 sec  34.6 MBytes   290 Mbits/sec
>     > > [  3] 30.0-31.0 sec  34.8 MBytes   292 Mbits/sec
>     > > [  3] 31.0-32.0 sec  34.8 MBytes   292 Mbits/sec
>     > > [  3] 32.0-33.0 sec  34.9 MBytes   293 Mbits/sec
>     >
>     > Do you use ath9k for that purpouse? I was thinking our driver is
>     not able to operate MIMO.
>     > Some changes that i missed?
> 
>     Yes, those numbers are with ath9k, with latest wireless-testing.
> 
> OK, tnx Sujith, but that brings me to my next question acc. 2x2 or 3x3
> on OpenWRT-based devices like NanoStation M or AirBridge M.
> Up to now only 1x2 or 1x3 was possible on this devices. Do we have
> changings there too?
Why do you think that only 1x2 or 1x3 was possible on these devices? 2x2
and 3x3 has been working just fine for a long time now, and it's enabled
by default where supported by the hardware.

- Felix

  parent reply	other threads:[~2012-05-26 12:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26  3:17 Anyone doing WiFi throughput tests? Ben Greear
2012-05-26  3:24 ` Sujith Manoharan
2012-05-26  5:48   ` [ath9k-devel] " Joe Semler
2012-05-26  7:43     ` Sujith Manoharan
     [not found]       ` <CAPsaeQPxh0Yd+GT3HbReAAtoPhKF2c3kOzgOPL6xK7NC=8J4qA@mail.gmail.com>
2012-05-26 11:28         ` Sujith Manoharan
2012-05-26 12:35         ` Felix Fietkau [this message]
2012-05-26 17:15           ` Joe Semler
2012-05-26 17:50             ` Adrian Chadd
     [not found]               ` <CAPsaeQNwWmAyzgGa3KjVv=nzwL3QHCDN-kHtaQWxKHOS4P+paA@mail.gmail.com>
2012-05-29 10:58                 ` Felix Fietkau
2012-05-26 18:27             ` Felix Fietkau
2012-05-26 15:37   ` Ben Greear
2012-05-26 16:24     ` Sujith Manoharan
2012-05-26 16:39       ` Sujith Manoharan
2012-05-27 15:08         ` Ben Greear
2012-05-27 17:40           ` Adrian Chadd
2012-05-27 18:14             ` Felix Fietkau
2012-05-27 23:15               ` Adrian Chadd
2012-05-27 23:29                 ` Felix Fietkau
2012-05-28  3:55             ` Ben Greear
2012-05-28  6:50               ` Adrian Chadd
2012-05-28  7:15                 ` Sujith Manoharan
2012-05-28 20:07                   ` Adrian Chadd
2012-05-31 19:24                     ` Adrian Chadd
2012-05-31 22:31                       ` Ben Greear
2012-05-29 18:23           ` [ath9k-devel] " Ben Greear
2012-05-29 19:07             ` Christian Lamparter
2012-05-29 19:19               ` Ben Greear
2012-05-30  0:06               ` Ben Greear
2012-05-30  3:22                 ` Dave Taht
2012-05-30  3:47                   ` Ben Greear
2012-05-31  2:29             ` Sujith Manoharan
2012-05-26 17:58     ` Christian Lamparter
2012-05-29  8:14       ` Zefir Kurtisi
2012-05-26 17:56 ` Adrian Chadd
2012-05-27  2:05   ` Sujith Manoharan
2012-05-27  2:09     ` [ath9k-devel] " Sujith Manoharan
2012-05-27  2:16       ` Ben Greear
2012-05-27  2:23         ` Sujith Manoharan
2012-05-27 11:30       ` Felix Fietkau
2012-05-27 12:32       ` Adrian Chadd
2012-05-27 12:31     ` Adrian Chadd

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=4FC0CE2B.9060005@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=c_manoha@qca.qualcomm.com \
    --cc=josef.semler@gmail.com \
    --cc=linux-wireless@vger.kernel.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).