ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Alexis Green <agreen@cococorp.com>, ath10k@lists.infradead.org
Subject: Re: Throughput weirdness on 9984
Date: Fri, 2 Sep 2016 14:51:17 -0700	[thread overview]
Message-ID: <35fa0be2-6ac6-0f7f-cb4e-e8bfced4199c@candelatech.com> (raw)
In-Reply-To: <CAAnMG+NUtOyxrzyXc4TyzPR8nuz2RcG80+GBwEZdfBFDknL2eQ@mail.gmail.com>

On 09/02/2016 02:11 PM, Alexis Green wrote:
> Hello,
>
> As I was working with ath10k drivers, I have discovered that only CT
> firmware/driver combination is able to report tx_info to mac80211
> layer. I've built latest LEDE image for my hardware (Netgear Nighthawk
> X4S R7800) with both ath10k-ct driver from Ben and CT firmware. This
> combination of software provides the data I need, however, the
> throughput is severely limited :/
>
> All tests are performed between two of these devices in mesh mode with
> no encryption. Here are some of the iperf results:

I have not actually tested mesh-mode on my firmware, so maybe I caused
regressions related to that.

If you use AP + STA config, is throughput better?

What about IBSS?

What tx/rx rates is CT firmware actually reporting?  Maybe it is not
enabling HT/VHT for some reason?

Thanks,
Ben

-- 
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:[~2016-09-02 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 21:11 Throughput weirdness on 9984 Alexis Green
2016-09-02 21:51 ` Ben Greear [this message]
2016-09-02 22:14   ` Alexis Green
2016-09-02 22:52     ` 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=35fa0be2-6ac6-0f7f-cb4e-e8bfced4199c@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=agreen@cococorp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox