General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] CAKE in openwrt high CPU
Date: Tue, 1 Sep 2020 15:01:13 -0400	[thread overview]
Message-ID: <07CD4278-D448-49D2-AC73-9C230EC041DE@jonathanfoulkes.com> (raw)
In-Reply-To: <87r1rliiiw.fsf@toke.dk>

Thanks Toke, we currently are on an MT7621a @880, so a dual-core.
And we are looking for a good quad-core platform that will support 600Mbps or more with Cake enabled, hopefully with AX radios as well.

Jonathan

> On Sep 1, 2020, at 12:11 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Jonathan Foulkes <jf@jonathanfoulkes.com> writes:
> 
>> Toke, that link returns a 404 for me.
> 
> Ah, seems an extra character snuck in at the end - try this:
> 
> https://github.com/dtaht/sch_cake/commit/3152477235c934022049fcddc063c45d37ec10e6
> 
>> For others, I’ve found that testing cake throughput with isolation options enabled is tricky if there are many competing connections. 
>> Like I keep having to tell my customers, fairness algorithms mean no one device will ever gain 100% of the bandwidth so long as there are other open & active connections from other devices.
>> 
>> That said, I’d love to find options to increase throughput for
>> single-tin configs.
> 
> Yeah, doing something about this is on my list, one way or another. Not
> sure how much more we can do in terms of overhead, so we may have to go
> for multi-q (and multi-CPU) support. How many CPU cores does the
> IQrouter have?
> 
> -Toke


  parent reply	other threads:[~2020-09-01 19:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 17:27 Mikael Abrahamsson
2020-08-30 17:52 ` Dave Taht
2020-08-31 11:35 ` Toke Høiland-Jørgensen
2020-08-31 12:22   ` Mikael Abrahamsson
2020-08-31 13:29     ` Toke Høiland-Jørgensen
2020-09-03 13:10       ` Mikael Abrahamsson
2020-09-03 13:29         ` Toke Høiland-Jørgensen
2020-09-03 13:34           ` Sebastian Moeller
2020-09-03 13:32         ` Sebastian Moeller
2020-09-04 13:37           ` Mikael Abrahamsson
2020-09-04 14:12             ` Sebastian Moeller
2020-09-01 15:41   ` Jonathan Foulkes
2020-09-01 16:11     ` Toke Høiland-Jørgensen
2020-09-01 16:25       ` Sebastian Moeller
2020-09-01 18:45         ` Toke Høiland-Jørgensen
2020-09-01 19:05           ` Jonathan Morton
2020-09-01 21:09             ` Toke Høiland-Jørgensen
2020-09-01 19:01       ` Jonathan Foulkes [this message]
2020-09-01 21:11         ` Toke Høiland-Jørgensen
2020-09-02 20:26           ` Jonathan Foulkes
2020-09-02 20:57             ` Toke Høiland-Jørgensen
2020-09-03 13:19           ` Mikael Abrahamsson
2020-09-03 13:27             ` Luca Muscariello
2020-09-03 14:32               ` Toke Høiland-Jørgensen
2020-09-03 15:31                 ` Luca Muscariello
2020-09-03 18:39                   ` Toke Høiland-Jørgensen
2020-09-03 18:53                 ` Jonathan Morton
2020-09-03 22:14                 ` [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU) David Collier-Brown
2020-09-04  1:19                   ` Jonathan Morton
2020-09-04 13:41                     ` Mikael Abrahamsson
2020-09-04 11:11                   ` Toke Høiland-Jørgensen
2020-09-03 13:27             ` [Bloat] CAKE in openwrt high CPU Toke Høiland-Jørgensen
2020-09-01 16:18     ` Sebastian Moeller
2020-09-01 19:31       ` Jonathan Foulkes
2020-09-01 20:04         ` Sebastian Moeller
2020-09-01 20:09           ` Jonathan Morton

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=07CD4278-D448-49D2-AC73-9C230EC041DE@jonathanfoulkes.com \
    --to=jf@jonathanfoulkes.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    --cc=toke@toke.dk \
    /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