ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: richard mayers <richard.mayers92@gmail.com>, ath10k@lists.infradead.org
Subject: Re: Fwd: Cannot achieve throughput higher than 460Mbps using CT firmware and 3x3 ath10k
Date: Thu, 07 May 2015 07:19:27 -0700	[thread overview]
Message-ID: <554B746F.8090803@candelatech.com> (raw)
In-Reply-To: <CAMCCUbhgc6f3kXNy5ESXahA5ypbPBH5dCrYcdp4atEUz9msD4w@mail.gmail.com>

You tried your antenna at different orientations?  Seems they work better
when they are somewhat orthogonal to each other.

Thanks,
Ben


On 05/07/2015 12:52 AM, richard mayers wrote:
> ---------- Forwarded message ----------
> From: richard mayers <richard.mayers92@gmail.com>
> Date: 2015-05-07 9:51 GMT+02:00
> Subject: Re: Cannot achieve throughput higher than 460Mbps using CT
> firmware and 3x3 ath10k
> To: Michal Kazior <michal.kazior@tieto.com>
>
>
> Hi,
>
> Yes, with only one spatial stream I can use MCS9 and I get 290Mbps
> more or less, then with 2 spatial streams I can also use MCS 8, but as
> I said with 3 streams  I only get a "good throughput" with  MC6.
>
> Richard
>
> 2015-05-07 7:47 GMT+02:00 Michal Kazior <michal.kazior@tieto.com>:
>> On 6 May 2015 at 17:01, richard mayers <richard.mayers92@gmail.com> wrote:
>>> Hi all,
>>>
>>> The maximum throughput I get with the following set up is around
>>> 460-470Mbits/s when using MCS 6, 80MHz channel and 3 spatial streams.
>>> However, when I try MCS 7, the throughput drops to 200Mbits/s, and
>>> when I use 8 or 9 it goes to 0. The signal level is -11dBm which I
>>> guess is quite good.
>>
>> Hmm.. From my experience too strong signal can degrade performance
>> with qca988x. You could try reducing it via `iw`. You could also try
>> checking if using only 2 spatial streams also yields problems with
>> MCS8 and MCS9.
>>
>> Antenna themselves might be the problem as well. Strong signal doesn't
>> mean good signal quality. If your antenna connector is damaged or
>> antenna is of poor quality you might end up not being able to use
>> highest MCS rates.
>>
>>
>> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

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

  reply	other threads:[~2015-05-07 14:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 15:01 Cannot achieve throughput higher than 460Mbps using CT firmware and 3x3 ath10k richard mayers
     [not found] ` <CABkMH_qT-xf4bROnnwRc=+wS9rOY6m-PMU63ertdUH-6X_jGVg@mail.gmail.com>
2015-05-06 15:46   ` Ben Greear
2015-05-07  5:47 ` Michal Kazior
     [not found]   ` <CAMCCUbgLheuDmqBb7yDp4zQ5Mxy4xfTUDYKSx8hF3OR6ATRf0w@mail.gmail.com>
2015-05-07  7:52     ` Fwd: " richard mayers
2015-05-07 14:19       ` Ben Greear [this message]
2015-05-07 16:04         ` richard mayers
2015-05-07 16:23           ` Ben Greear
2015-05-07 17:00 ` Pushpal Sidhu
2015-05-07 18:01   ` richard mayers
2015-05-07 19:33     ` Pushpal Sidhu

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=554B746F.8090803@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=richard.mayers92@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