From: Dave Taht <dave.taht@gmail.com>
To: Noah Causin <n0manletter@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>,
Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [Make-wifi-fast] wifi airtime fairness patches could use eyeballs and testing
Date: Sun, 14 Aug 2016 15:21:21 -0700 [thread overview]
Message-ID: <CAA93jw7cK6Cg1a5uN=d3u4x3RNM_ZSuiCLK4ig9+TY71iZadsg@mail.gmail.com> (raw)
In-Reply-To: <76eb6a6a-2f39-3b36-d4c1-04198083c0f6@gmail.com>
Toke and I have now done a great deal of testing and exploration of
the issue with leaving "fq" enabled on the ath9k (running with and
without felix's patch).
The only thing we've found that "moves the bar" is the presence or
absence of crypto. With crypto + fq on, on the wndr 3800, we see a
significant performance variation of 32-80mbit as the number of flows
goes from 12 to 1.
without crypto, with or with fq enabled, we are able to reliably get
120Mbits on our test setup.
The patterns of the degradation are also often variable, we will have
long periods where things are quite stable, and other 10-20 sec
periods where throughput drops or stops almost entirely.
It would be nice to get confirmation that the fq is working without
crypto enabled.
Ideas as to why crypto chops off so much throughput in the first place
(from 120mbit to 80), and as to what else to poke into with crypto on,
would be nice.
next prev parent reply other threads:[~2016-08-14 22:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 11:28 Dave Taht
2016-08-10 13:06 ` Noah Causin
2016-08-10 13:11 ` Dave Taht
2016-08-10 14:47 ` [Make-wifi-fast] [Cerowrt-devel] " Dave Täht
2016-08-10 15:04 ` [Make-wifi-fast] " Toke Høiland-Jørgensen
2016-08-10 19:35 ` Dave Taht
2016-08-10 20:06 ` Toke Høiland-Jørgensen
2016-08-10 21:50 ` Toke Høiland-Jørgensen
2016-08-10 21:58 ` Dave Taht
2016-08-10 22:05 ` Toke Høiland-Jørgensen
2016-08-10 22:07 ` Toke Høiland-Jørgensen
2016-08-10 22:18 ` Jonathan Morton
2016-08-10 22:45 ` Toke Høiland-Jørgensen
2016-08-11 6:43 ` Dave Taht
2016-08-11 9:16 ` Toke Høiland-Jørgensen
2016-08-11 9:38 ` Jeremy Harris
2016-08-14 22:21 ` Dave Taht [this message]
2016-08-14 22:49 ` [Make-wifi-fast] [Cerowrt-devel] " Aaron Wood
2016-08-14 23:02 ` Dave Taht
2016-08-14 23:04 ` Aaron Wood
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='CAA93jw7cK6Cg1a5uN=d3u4x3RNM_ZSuiCLK4ig9+TY71iZadsg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=n0manletter@gmail.com \
--cc=nbd@nbd.name \
--cc=sw@simonwunderlich.de \
/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