From: "KAVITA MATHUR" <kavitam@cdot.in>
To: Ben Greear <greearb@candelatech.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: Throughput drop with ath10k latest driver and firmware-5.bin_10.2.4.70.66
Date: Fri, 27 Oct 2017 13:55:22 +0530 [thread overview]
Message-ID: <20171027081929.M60415@cdot.in> (raw)
In-Reply-To: <df6008fe-79e0-ce06-c191-8557e11f1b3a@candelatech.com>
On Thu, 26 Oct 2017 07:48:18 -0700, Ben Greear wrote
> On 10/26/2017 04:20 AM, KAVITA MATHUR wrote:
> > Hi,
> >
> > In my AP , there are two radios, one ath9k based module WLE200NX and second ath10k based
> > WLE600VX.
> >
> > I configured both the radios as AP in IEEE 802.11a 40 MHz HT mode and performed
> > throughput test.
> >
> > Measured throughput with ath9k is 164Mbps while with ath10k it is 137Mbps. I could not
> > understand the reason of this drop(27 Mbps)?
> >
> > My test setup was inside RF-Shield. There was no interference and system was associated
> > at 300Mbps in both cases.
> >
> > ath10k driver was taken from ath10k git and firmware version is
> > firmware-5.bin_10.2.4.70.66.
> > ath9k drives was taken from stable backport release backport-4.4.2-1.
> >
> > kernel version : 3.12
> > openwrt version : Chaos Calmer 15.05.0
> >
> > Please suggest me how can I increase the throughput of my AP.
>
> Does it work any better with different firmware/software, or is ath10k just
> always slower for you?
Yes. Measured throughput in the same configuration was 193 Mbps when used ath10k driver
from backport stable release backport-4.4.2-1 and firmware version
firmware-5.bin_10.2.4.70.63-2. But this version is not stable for ac mode and it does
not support MESH. Please suggest appropriate ath10k driver version and firmware.
>
> How much attenuation are you using?
Received Signal strength is -38 dBm and tx power is 5dBm in all these testcases.
> Thanks,
> Ben
>
> >
> >
> >
> >
> > Thanks & Regards,
> > कविता माथुर Kavita Mathur
> > वरिष्ठ अनुसंधान अभियंता Senior Research Engineer
> > सी-डॉट C-DOT
> > इलैक्ट्रॉनिक्स सिटी फेज़ I Electronics City Phase I
> > होसूर रोड, बेंगलूरु Hosur Road, Bengaluru – 560100
> > फोन Ph 080-28529896
> > Disclaimer:
> > ----------
> > This email and any files transmitted with it
> >
> >
> > _______________________________________________
> > 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
Thanks & Regards,
कविता माथुर Kavita Mathur
वरिष्ठ अनुसंधान अभियंता Senior Research Engineer
सी-डॉट C-DOT
इलैक्ट्रॉनिक्स सिटी फेज़ I Electronics City Phase I
होसूर रोड, बेंगलूरु Hosur Road, Bengaluru – 560100
फोन Ph 080-28529896
Disclaimer:
----------
This email and any files transmitted with it
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-27 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 11:20 Throughput drop with ath10k latest driver and firmware-5.bin_10.2.4.70.66 KAVITA MATHUR
2017-10-26 14:48 ` Ben Greear
2017-10-27 8:25 ` KAVITA MATHUR [this message]
2017-10-27 16:49 ` 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=20171027081929.M60415@cdot.in \
--to=kavitam@cdot.in \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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