From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel\@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] wifi airtime fairness patches could use eyeballs and testing
Date: Wed, 10 Aug 2016 23:50:03 +0200 [thread overview]
Message-ID: <87bn109tv8.fsf@toke.dk> (raw)
In-Reply-To: <E8B9BE5E-CBDD-4F7D-8390-9A4415FEBA95@toke.dk> ("Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen=22's?= message of "Wed, 10 Aug 2016 22:06:39 +0200")
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> On 10 August 2016 21:35:40 CEST, Dave Taht <dave.taht@gmail.com> wrote:
>>Wow, that *is* weird. It is good to see the tcp window changing on
>>this set of data (it wasn't before), and CWRs, but... hmmm... SCIENCE.
>>
>>Enabling ecn on both sides will rule out some potential bugs.
>
> Yeah, couldn't get ecn to work on the host I was using as the other endpoint on
> that test. Will try with another box that's not on quite as ancient a kernel.
> Was also planning to disable codel (by setting a very high target) to try to
> narrow down the problem.
OK, digging some more on this:
I am seeing *no* drops by CoDel, and no backlog in the mac80211 softq
layer either (or at most one or two packets when polling with a 1 sec
interval). This is with one as well as with two flows.
On my x86 testbed I see backlog building and packets getting dropped by
CoDel - and can't reproduce the performance hit. So I'm wondering what
the difference is. I can think of:
- Another bottleneck somewhere in the system limiting things on the
wndr3800.
- A locking issue in the FQ mechanism preventing packets from being
queued properly.
- Something related to the wndr only having a single CPU.
-Toke
next prev parent reply other threads:[~2016-08-10 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 11:28 [Cerowrt-devel] " Dave Taht
2016-08-10 13:06 ` [Cerowrt-devel] [Make-wifi-fast] " Noah Causin
2016-08-10 13:11 ` Dave Taht
2016-08-10 15:04 ` 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 [this message]
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-14 22:21 ` Dave Taht
2016-08-14 22:49 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn109tv8.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nbd@nbd.name \
/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