From: Felix Fietkau <nbd@nbd.name>
To: Dave Taht <dave.taht@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Michal Kazior" <michal.kazior@tieto.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Make-wifi-fast] TCP performance regression in mac80211 triggered by the fq code
Date: Tue, 12 Jul 2016 13:21:25 -0000 [thread overview]
Message-ID: <097af8e4-5393-8e1b-1748-36233e605867@nbd.name> (raw)
In-Reply-To: <CAA93jw6=_pemSUjk3dje1GmnTzrs+=pEdza4j1Wjtrw+VKNdNg@mail.gmail.com>
On 2016-07-12 14:13, Dave Taht wrote:
> On Tue, Jul 12, 2016 at 12:09 PM, Felix Fietkau <nbd@nbd.name> wrote:
>> Hi,
>>
>> With Toke's ath9k txq patch I've noticed a pretty nasty performance
>> regression when running local iperf on an AP (running the txq stuff) to
>> a wireless client.
>
> Your kernel? cpu architecture?
QCA9558, 720 MHz, running Linux 4.4.14
> What happens when going through the AP to a server from the wireless client?
Will test that next.
> Which direction?
AP->STA, iperf running on the AP. Client is a regular MacBook Pro
(Broadcom).
>> Here's some things that I found:
>> - when I use only one TCP stream I get around 90-110 Mbit/s
>
> with how much cpu left over?
~20%
>> - when running multiple TCP streams, I get only 35-40 Mbit/s total
> with how much cpu left over?
~30%
> context switch difference between the two tests?
What's the easiest way to track that?
> tcp_limit_output_bytes is?
262144
> got perf?
Need to make a new build for that.
>> - fairness between TCP streams looks completely fine
>
> A codel will get to long term fairness pretty fast. Packet captures
> from a fq will show much more regular interleaving of packets,
> regardless.
>
>> - there's no big queue buildup, the code never actually drops any packets
>
> A "trick" I have been using to observe codel behavior has been to
> enable ecn on server and client, then checking in wireshark for ect(3)
> marked packets.
I verified this with printk. The same issue already appears if I have
just the fq patch (with the codel patch reverted).
>> - if I put a hack in the fq code to force the hash to a constant value
>
> You could also set "flows" to 1 to keep the hash being generated, but
> not actually use it.
>
>> (effectively disabling fq without disabling codel), the problem
>> disappears and even multiple streams get proper performance.
>
> Meaning you get 90-110Mbits ?
Right.
> Do you have a "before toke" figure for this platform?
It's quite similar.
>> Please let me know if you have any ideas.
>
> I am in berlin, packing hardware...
Nice!
- Felix
next prev parent reply other threads:[~2016-07-12 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11fa6d16-21e2-2169-8d18-940f6dc11dca@nbd.name>
2016-07-12 12:13 ` Dave Taht
2016-07-12 13:21 ` Felix Fietkau [this message]
2016-07-12 14:02 ` Dave Taht
2016-07-13 7:57 ` Dave Taht
2016-07-13 8:53 ` Felix Fietkau
2016-07-13 9:13 ` Dave Taht
2016-07-19 13:10 ` Michal Kazior
[not found] ` <87shvfujl4.fsf@toke.dk>
[not found] ` <CAA93jw6z53P+JCPsjYD-vaY+9vq9ZO-Ob_cXm0AE76uVcM=F9g@mail.gmail.com>
[not found] ` <87bn23ui87.fsf@toke.dk>
2016-07-12 13:03 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=097af8e4-5393-8e1b-1748-36233e605867@nbd.name \
--to=nbd@nbd.name \
--cc=dave.taht@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michal.kazior@tieto.com \
--cc=toke@toke.dk \
/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