Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Imre Kaloz" <kaloz@openwrt.org>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	cake@lists.bufferbloat.net, "Dave Taht" <dave.taht@gmail.com>
Subject: Re: [Cake] linksys ac1200 network bug
Date: Sat, 28 Nov 2015 22:19:24 +0100	[thread overview]
Message-ID: <op.x8tximc22s3iss@ecaz> (raw)
In-Reply-To: <CAA93jw7pBE_YrhK=OAKzVku6gKP7FB4aZNM20c+tHoCyu7bj0A@mail.gmail.com>

Did you see https://lkml.org/lkml/2015/11/27/325 ? I'll try to find time  
to integrate a newer kernel and that patchset as well as  
https://lkml.org/lkml/2015/11/22/9 ,  
http://lkml.iu.edu/hypermail/linux/kernel/1511.0/04354.html and  
http://lists.openwall.net/netdev/2015/09/25/151


Imre

On Sat, 28 Nov 2015 15:41:17 +0100, Dave Taht <dave.taht@gmail.com> wrote:

> I went for a test drive of openwrt DESIGNATED DRIVER (Bleeding Edge,
> r47665) today.
>
> A) I bricked the archer c7 v2. No idea why.
>
> B) I got a sorta working linksys 1200ac build.
>
> The bad news: Any attempt to run 2 or more copies of netperf's
> netserver on the 1200ac router with the default qdiscs (mq +
> fq_codel), at line (gbit) rate, result in it locking up *for any other
> traffic, including ping* until the first netperf is more or less
> complete. I fear the underlying driver is  frightfully overbuffered,
> or has another problem.
>
> http://snapon.cs.kau.se/~d/archer-c7/onenetperflockout.png
>
> (needs BQL, too)
>
> The still bad news: cake works in both directions for a while longer,
> then goes boom similarly.
>
> The somewhat good news:
>
> cake "shaped" to 900mbit on inbound and outbound to the router - does
> not lock up the router. It merely runs out of cpu, but still does
> manage quite respectable throughput in both  directions while doing
> so. Note, I did not say "latency".
>
> http://snapon.cs.kau.se/~d/archer-c7/encouraged.png
>
> As usual there is some flent data in that dir if you want to draw your
> own plots.
>
> I was not in a position to actually test traffic through the router
> (because I had the archer setup to do that)
>
> I wouldn't draw any conclusions from this. Well, a safe conclusion,
> is: don't install this build.
>
> On Sat, Nov 28, 2015 at 11:41 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> Trying to do my first openwrt build in a while.
>>
>> make[5]: Leaving directory
>> '/home/cero4/src/archer-c7/build_dir/target-mips_34kc_musl-1.1.11/dante-1.2.2'
>> Makefile:349: recipe for target 'all' failed
>>
>> I checked: the package "dante" is not installed. Nor can I figure out
>> what package is arbitrarily requiring it.
>>
>> I truly am in hell.
>
> Simple patch for this, It involves invoking a deity.
>
>
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> https://www.gofundme.com/savewifi

  parent reply	other threads:[~2015-11-28 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 14:41 Dave Taht
2015-11-28 14:45 ` Dave Taht
2015-11-28 17:37   ` Dave Taht
2015-11-28 17:46     ` Kevin Darbyshire-Bryant
2015-11-28 18:02       ` Dave Taht
2015-11-28 21:19 ` Imre Kaloz [this message]
2015-11-29 11:18   ` 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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.x8tximc22s3iss@ecaz \
    --to=kaloz@openwrt.org \
    --cc=cake@lists.bufferbloat.net \
    --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