All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Jooris <Bart.Jooris@intec.ugent.be>
To: ath10k@lists.infradead.org
Subject: Re: Running throughput tests
Date: Fri, 28 Mar 2014 16:11:07 +0100	[thread overview]
Message-ID: <5335910B.3000702@intec.ugent.be> (raw)
In-Reply-To: <87y50weecb.fsf_-_@kamboji.qca.qualcomm.com>

Dear Kalle,

On 02/27/2014 04:59 PM, Kalle Valo wrote:
> Changing subject.
>
> Bart Jooris<Bart.Jooris@intec.ugent.be>  writes:
>
>> Just got a stable 160Mbps (iperf udp, tweeking the distance and ended
>> up around 50cm) on a Ubuntu 13.10 client (regulatory.bin still not
>> ok).
>> Not yet the 300Mbps as I read earlier on the thread.
>> What could be the next steps to speed up the link?
> First I would use the full hostapd configuration which I just added to
> the wiki:
>
> http://wireless.kernel.org/en/users/Drivers/ath10k/configuration#Full_hostapd_configuration
>
> Next I would disable all possible debug features from kernel and make
> sure that they are not included in the build. And last try to find a
> free channel with little interference as possible.
>
> I'm sure others have better ideas.
>
No luck for now. 160Mbps seems to be the limit using the mentioned 
configuration (I had to fix the channel to 36 and add 
vht_oper_centr_freq_seg0_idx=42 again to bring up the AP)
I'm using sparkLAN WPEA-351AC cards with QCA9880 chip set.
I' ve got this info from SparkLAN:

On 03/03/2014 11:35 AM, (SparkLAN) wrote:
> It seems like you are trying to test on AP mode with DFS band, but 
> unfortunately Ath9K and 10K does not support that so far. 

You are probably using Compex cards with the same chip set?
Based on the chip set, I should be able to get higher bitrates or is it 
possbile that the WPEA-351AC card needs another configuration?

Thanks a lot,

Bart


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

  reply	other threads:[~2014-03-28 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00ea01cee403$5331f1e0$f995d5a0$@sparklan.com>
     [not found] ` <00d101cee597$e8c57480$ba505d80$@sparklan.com>
     [not found]   ` <52A592B7.9000806@intec.ugent.be>
     [not found]     ` <006301cef71c$d850ec10$88f2c430$@sparklan.com>
     [not found]       ` <52A98706.7080907@intec.ugent.be>
     [not found]         ` <008d01cef722$2a9c05e0$7fd411a0$@sparklan.com>
     [not found]           ` <52A9DEF9.8080305@intec.ugent.be>
     [not found]             ` <012e01cef7e0$99017e70$cb047b50$@sparklan.com>
     [not found]               ` <52AACFB9.8080901@intec.ugent.be>
     [not found]                 ` <006301cefa3c$44c07b50$ce4171f0$@sparklan.com>
     [not found]                   ` <52AEC26B.2060400@intec.ugent.be>
     [not found]                     ` <007f01cefa41$8a940de0$9fbc29a0$@sparklan.com>
     [not found]                       ` <52AEE61F.5030505@intec.ugent.be>
     [not found]                         ` <006b01cefacb$6c0b2d60$44218820$@sparklan.com>
     [not found]                           ` <52B00B10.3050300@intec.ugent.be>
     [not found]                             ` <004b01cefb9d$04a543e0$0defcba0$@sparklan.com>
     [not found]                               ` <52B2AE75.9050206@intec.ugent.be>
     [not found]                                 ` <00df01cf0090$05944f10$10bced30$@sparklan.com>
     [not found]                                   ` <52B9672E.9000701@intec.ugent.be>
     [not found]                                     ` <008c01cf012e$e59563d0$b0c02b70$@sparklan.com>
2014-02-23 21:15                                       ` nl80211: Failed to set channel Bart Jooris
2014-02-24  8:44                                         ` Sven Schnelle
2014-02-24  9:02                                           ` Kalle Valo
2014-02-24 14:59                                           ` Bart Jooris
     [not found]                                           ` <530E5EF2.8070800@intec.ugent.be>
2014-02-27 15:59                                             ` Running throughput tests Kalle Valo
2014-03-28 15:11                                               ` Bart Jooris [this message]
2014-03-28 15:31                                                 ` Kalle Valo
2014-03-29 19:42                                                   ` Bart Jooris
2014-03-29 20:18                                                     ` Ben Greear
2014-03-30  7:31                                                       ` Bart Jooris
2014-03-30 17:06                                                         ` Ben Greear
2014-04-08 12:45                                                         ` Kalle Valo
2014-03-30  9:36                                                     ` Bart Jooris
2014-04-08 12:42                                                     ` Kalle Valo
2014-04-19 19:48                                                       ` Bart Jooris
2014-04-24  6:44                                                         ` Kalle Valo
2014-04-29  3:55                                                           ` Ben Greear
2014-05-12  4:37                                                             ` Kalle Valo
2014-05-12  4:44                                                               ` Ben Greear
2014-05-12  5:14                                                                 ` Kalle Valo

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=5335910B.3000702@intec.ugent.be \
    --to=bart.jooris@intec.ugent.be \
    --cc=ath10k@lists.infradead.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 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.