From: Christian Lamparter <chunkeey@googlemail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Sujith Manoharan <c_manoha@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: Anyone doing WiFi throughput tests?
Date: Sat, 26 May 2012 19:58:22 +0200 [thread overview]
Message-ID: <201205261958.22934.chunkeey@googlemail.com> (raw)
In-Reply-To: <4FC0F8CE.1030303@candelatech.com>
On Saturday 26 May 2012 17:37:50 Ben Greear wrote:
> We're using WPEA-127N. We have a dual-core Atom for one system, and
> a quad-core i7 CPU (and two wifi NICs) in another system.. So far,
> the Atom with single NIC is benchmarking better in some tests. We
> were only using one of the NICs in the i7 for testing, but maybe
> there is still some interference or maybe we just had bad antenna
> placement or something.
>
> We've used various Asus and Netgear APs...haven't done throughput
> tests with home-grown APs running Atheros NICs recently, but will
> do so next week.
>
> > With a XB112 card (3x3) in HT40 mode, 5Ghz, TX throughput (TCP) can reach 290 Mbps.
>
> What chipset or brand/model is this? I see that XB112 mentioned
> in the WPEA-127N description, but maybe that is just a form-factor
> description?
Well, Atheros made some nice presentations about that:
<http://wenku.baidu.com/view/ac0523f57c1cfad6195fa7f4.html>
take a look at slide 12. It has 11n technology (2x2 vs
3x3 ZF vs ML vs CC vs LDPC vs (TxBF) vs range vs tcp
throughput all on one diagramm)
Regards,
Chr
next prev parent reply other threads:[~2012-05-26 17:58 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
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 [this message]
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=201205261958.22934.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=c_manoha@qca.qualcomm.com \
--cc=greearb@candelatech.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).