From: Ben Greear <greearb@candelatech.com>
To: Cedric VONCKEN <cedric.voncken@acksys.fr>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: ATH10 firmware question
Date: Tue, 24 Nov 2015 13:29:12 -0800 [thread overview]
Message-ID: <5654D6A8.9050002@candelatech.com> (raw)
In-Reply-To: <773DB8A82AB6A046AE0195C68612A31901C5AFA5@sbs2003.acksys.local>
On 11/24/2015 10:07 AM, Cedric VONCKEN wrote:
> Hi,
>
> I have a simple test platform.
> One PC connected to an equipment. This equipment is set in AP
> mode.
> Another PC connected to another equipment. This equipment is set
> in STA + WDS mode.
>
> Both equipment use the same openwrt Firmware (compat
> 2015-07-21), I only changed the ath10k firmware (in
> /lib/firmware/ath10k/...).
> Both equipment has the same hardware.
> I used a clear channel, and VHT80.
> The radio was connected with a coaxial cable and I placed 40 dBm
> attenuation per Rf chain.
> I used the WLN350NX radio card from compex.
>
> First test : ATH10K firmware 10.2.4.70-2 on both equipment
> An iperf from PC connected to the AP to the PC connected
> to the STA give 919 Mbps.
> An iperf from PC connected to the STA to the PC
> connected to the AP give 500 Mbps.
>
> Second test : ATHK firmware 10.2.4.70.10-2 on both equipment
> An iperf from PC connected to the AP to the PC connected
> to the STA give 921 Mbps.
> An iperf from PC connected to the STA to the PC
> connected to the AP give 441 Mbps.
>
> If I cross the computer I have the same result. I did several
> time these test and I always have the same result.
We see similar. One thing we notice is that if you actually try to send less
throughput, then you get better overall throughput.
In other words, trying to send 1Gbps UDP frames will give you more poor
throughput than trying to send 650Mbps (in the upload direction).
I thought it might be a poor interaction regarding backoff in the
ath10k driver/firmware (see the congestion bins in firmware for why
this is the case), but even fixing that in firmware didn't improve
the situation in my testing.
Thanks,
Ben
>
> Is it the expected result?
> What is the recommanded firmware version for each mode?
>
> Thanks for your help.
>
> Cedric Voncken.
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-11-24 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:07 ATH10 firmware question Cedric VONCKEN
2015-11-24 21:29 ` Ben Greear [this message]
2015-11-25 4:19 ` Michal Kazior
2015-11-25 6:19 ` Ben Greear
2015-11-25 10:41 ` voncken
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=5654D6A8.9050002@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=cedric.voncken@acksys.fr \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).