From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Robert Jones <rjones@gateworks.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Bad TCP performance on WLE900VX
Date: Thu, 4 Jan 2018 14:38:14 +0000 [thread overview]
Message-ID: <87vagh7kq2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CALAE=UAPXYsCfO+QXxPsnEe2vkcMcCoknSAc8RVyOVk85MC-8Q@mail.gmail.com> (Robert Jones's message of "Tue, 2 Jan 2018 17:47:18 -0800")
Robert Jones <rjones@gateworks.com> writes:
> Hello Everyone,
>
> I'm using a custom arm64 board with a Cavium CN8030 CPU and testing
> wireless card performance via iperf on Ubuntu 16.02 with a mainline
> 4.14 kernel. I have two identical units connected to each other via
> 60dB attenuators on all three channels. Channel is set to 161 VHT80.
>
> With UDP I see throughput upwards of 650Mbits/s, but TCP is
> ~24Mbits/s. That seemed odd so I did a little more testing. Switched
> to a 4.9 kernel and still saw the poor performance, but not with a
> 4.4. Before I went through the trouble of bisecting I thought to ask
> if there was something I was missing.
>
> I did come across this Ubuntu bug thread
> [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041] which
> appeared to follow the same behavior I was seeing. Switched my TCP
> congestion algorithm to reno and saw throughput jump to >330Mbits/s.
> Cubic and BBR still ~24.
>
> My question now, is there a standing bug that I'm not aware of or
> could there be some sort of problem with my configuration that is
> being worked around with the reno algorithm?
There's now support in TCP stack (commit below) to workaround this issue
in ath10k. I tried to come up with a patch before holidays but didn't
make it, anyone willing to write one?
tcp: allow drivers to tweak TSQ logic
https://git.kernel.org/linus/3a9b76fd0db9f0d426533f96a68a62a58753a51e
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-01-04 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 1:47 Bad TCP performance on WLE900VX Robert Jones
2018-01-03 2:00 ` Ben Greear
2018-01-04 14:38 ` Kalle Valo [this message]
2018-01-10 18:15 ` Robert Jones
2018-01-11 22:50 ` Ben Greear
2018-01-12 1:24 ` Robert Jones
2018-01-12 8:56 ` Sebastian Gottschall
2018-01-12 17:23 ` Robert Jones
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=87vagh7kq2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=rjones@gateworks.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