ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone have a working hostapd conf file for AC?
Date: Thu, 27 Feb 2014 15:53:28 +0200	[thread overview]
Message-ID: <87k3cgfyqv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAEFj985joW0f6EnOriFoY6cLSQVSBEj7jc5JQMjG0wXPt54NKg@mail.gmail.com> (Yeoh Chun-Yeow's message of "Thu, 27 Feb 2014 21:42:32 +0800")

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

>> With this I can get around 380Mbps TCP throughput downloading,
>> over the air, using the .467 firmware.  I have not yet tried to
>> do any significant tuning to improve this throughput.
>
> Quite impressive. Is this tested using iperf? I saw that even though
> the rx rate is MCS9 NSS 3 SGI 80MHz. I only get about 98Mbps TCP
> throughput using IPerf.

Huh, that's really bad. I haven't done any throughput tests for months,
but when I did I was able to easily get over 500 Mbps with iperf TCP OTA
tests (can't remember if TX or RX was better). This was on an x86
laptop.

When running throughput tests make sure to disable all possible kernel
debugging you have. Starting from CONFIG_ATH10K_DEBUG all the way to
slub debugging etc.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-02-27 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 22:00 Anyone have a working hostapd conf file for AC? Ben Greear
2014-02-26  0:19 ` Avery Pennarun
2014-02-26  0:51   ` Ben Greear
2014-02-26  1:08     ` Avery Pennarun
2014-02-26  6:23   ` Bartosz Markowski
2014-02-26 17:37 ` Kalle Valo
2014-02-26 17:46   ` Ben Greear
2014-02-26 22:42     ` Ben Greear
2014-02-27 13:42       ` Yeoh Chun-Yeow
2014-02-27 13:53         ` Kalle Valo [this message]
2014-02-27 16:51         ` Ben Greear

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=87k3cgfyqv.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=yeohchunyeow@gmail.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