Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Pete Heist <pete@heistp.net>,
	Cake List <cake@lists.bufferbloat.net>,
	 cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cake] apu2 sqm/htb issue + a minor win for speeding up fq_codel itself
Date: Wed, 3 Oct 2018 07:45:35 -0700	[thread overview]
Message-ID: <CAA93jw6a5ce5+HM6tnVXXwF+QcVNbmrsAf4jRBXSAsOAnjZF1g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7nGhSOsrZr5PuoReqQkVuB4JsjyOvQhimHOopWw0UmPg@mail.gmail.com>

at least, the bsd version issues may have settled down somewhat:
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/553
On Wed, Oct 3, 2018 at 7:44 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> On Wed, Oct 3, 2018 at 6:56 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> >
> > On Thu, 6 Sep 2018, Dave Taht wrote:
> >
> > > I put a bug here. Someone with a non apu product struggling with
> > > shaping (edgerouter? omnia?)
> > >
> > > https://github.com/tohojo/sqm-scripts/issues/71
> >
> > Yes, I have the same problem. My WRT1200AC (Marvell Armada 385) has
> > seriously degraded performance in OpenWrt 18.06.1 compared to whatever was
> > in in 17.01.x, I'd say factor 3-4 worse.
>
> OK, I'm basically seeing that too on the same hardware. I can barely
> shape 100Mbit inbound, But it's not cake, fq_codel is also running out
> of cpu.
>
> I *think*, but am not sure, this box could do a lot more prior to
> this, but I never really tried. I'm off mostly debugging a babel
> problem at the moment,
> and (sigh), having no ipv6, a babel bug, and a severe performance hit
> thus far in this release is depressing as hell.
>
> life was better for everyone when we spent more time rigorously
> testing stuff before it got released. I still have one
> good ole 'cerowrt box online, no money coming in, and while I did get
> a reprieve on having to close up the lab, I have to give up the yurt
> shortly.
>
>
>
> >
> > --
> > Mikael Abrahamsson    email: swmike@swm.pp.se
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-10-03 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 19:59 [Cerowrt-devel] " Dave Taht
2018-09-04 21:14 ` Dave Taht
2018-09-04 21:16   ` Dave Taht
2018-09-06 17:51     ` [Cerowrt-devel] [Cake] " Pete Heist
2018-09-06 18:03       ` Dave Taht
2018-10-03 13:56         ` Mikael Abrahamsson
2018-10-03 14:44           ` Dave Taht
2018-10-03 14:45             ` Dave Taht [this message]
2018-10-03 15:30             ` Mikael Abrahamsson
2018-10-03 16:05               ` Dave Taht
2018-10-03 17:43                 ` Toke Høiland-Jørgensen
2018-10-03 17:53                   ` Dave Taht
2018-10-03 18:32                   ` Jonathan Morton
2018-10-03 20:12                     ` Toke Høiland-Jørgensen
2018-10-05 12:52               ` Mikael Abrahamsson

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=CAA93jw6a5ce5+HM6tnVXXwF+QcVNbmrsAf4jRBXSAsOAnjZF1g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=pete@heistp.net \
    --cc=swmike@swm.pp.se \
    /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