From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] linksys 1200ac lockout problem still exists
Date: Sun, 20 Nov 2016 21:24:56 +0100 [thread overview]
Message-ID: <8D20D7C0-6736-4EED-B058-644747640E81@gmx.de> (raw)
In-Reply-To: <CAA93jw5dM2Xzg9=E8BKzpK+74=_d=c02QVjAKCOo7m8FFAiXAQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2677 bytes --]
Hi Dave,
when I use tcp_12down instead of tcp_ndown I end up with something looking sane (see attached image?)
Also:
Summary of tcp_12down test run at 2016-11-20 20:16:54.350770:
avg / median # data pts
Ping (ms) ICMP : 54.08 / 53.75 ms 351
TCP download avg : 3.52 / 3.57 Mbits/s 301
TCP download sum : 42.24 / 42.79 Mbits/s 301
TCP download::1 : 3.50 / 3.63 Mbits/s 301
TCP download::10 : 3.55 / 3.61 Mbits/s 301
TCP download::11 : 3.57 / 3.62 Mbits/s 301
TCP download::12 : 3.54 / 3.66 Mbits/s 300
TCP download::2 : 3.51 / 3.61 Mbits/s 300
TCP download::3 : 3.55 / 3.61 Mbits/s 301
TCP download::4 : 3.59 / 3.67 Mbits/s 300
TCP download::5 : 3.46 / 3.55 Mbits/s 300
TCP download::6 : 3.49 / 3.60 Mbits/s 301
TCP download::7 : 3.50 / 3.59 Mbits/s 300
TCP download::8 : 3.48 / 3.57 Mbits/s 301
TCP download::9 : 3.50 / 3.58 Mbits/s 300
looks fine. But maybe tcp_12down is not exactly doing the same as tcp_ndown… I tested from a laptop attached to one of the omnia’s lan ports (omnia’s wan is connected to the lan port of a LEDE r2222 wndr3700v2 with double NAT).
Best Regards
Sebastian
> On Nov 20, 2016, at 20:30, Dave Taht <dave.taht@gmail.com> wrote:
>
> Has the omnia got this problem?
>
> On Sun, Nov 20, 2016 at 11:29 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> so, in a flood of optimism, I reflashed my linksys 1200ac with lede head.
>>
>> If you hit it with more than one download flow in netperf(flent), all
>> successor flows still starve.
>>
>> http://www.taht.net/~d/linksys1200aclockout.png
>>
>> I was under the impression a fix (also adding BQL) had arrived for
>> this problem in mainline.
>>
>> filed a bug on it just now, I should have done so long ago.
>>
>> https://bugs.lede-project.org/index.php?do=details&task_id=294
>>
>> --
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> http://blog.cerowrt.org
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2.1: Type: text/html, Size: 5304 bytes --]
[-- Attachment #2.2: tcp_12down_20161120.png --]
[-- Type: image/png, Size: 40178 bytes --]
prev parent reply other threads:[~2016-11-20 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 19:29 Dave Taht
2016-11-20 19:30 ` Dave Taht
2016-11-20 19:43 ` Toke Høiland-Jørgensen
2016-11-20 20:13 ` Sebastian Moeller
2016-11-20 20:32 ` Toke Høiland-Jørgensen
2016-11-20 20:36 ` Dave Taht
2016-11-20 20:45 ` Sebastian Moeller
2016-11-20 20:45 ` Toke Høiland-Jørgensen
2016-11-20 20:48 ` Toke Høiland-Jørgensen
2016-11-20 20:24 ` Sebastian Moeller [this message]
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=8D20D7C0-6736-4EED-B058-644747640E81@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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