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: Wed, 2 Sep 2020 16:26:12 -0400 [thread overview]
Message-ID: <99EE16A1-6CC9-4EB6-A6DC-CE2E910C6ADE@jonathanfoulkes.com> (raw)
In-Reply-To: <87imcxi4mq.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
> Right, so some benefit might be possible here. Does the NIC have
> multiple hardware queues (`ls /sys/class/net/$IFACE/queues` should tell
> you)?
Here is the output of:
/sys/devices/virtual/net/eth0.2/queues# ls
rx-0 tx-0
/sys/devices/virtual/net/eth0.2/queues/rx-0# cat rps_cpus
0
/sys/devices/virtual/net/eth0.2/queues/tx-0# cat xps_cpus
0
> Yup, the number of cores is only going to go up, so for CAKE to stay
> relevant it'll need to be able to take advantage of this eventually :)
True, the mid-range market is already there, and so soon will be the lower-end.
And with ISPs lighting up more and more capacity, the demand will be there to be able to shape higher and higher rates.
But I agree with Jonathan Morton that once every deice has sufficient capacity, more makes no difference.
I went for 100/15 to 300/24 and never noticed the difference.
Hell, there are days I switch to my backup 10/0.7 DSL line for a test, and forget to switch back, and will work for hours and not notice I’m not on the 300Mbps line ;-)
Cheers,
Jonathan
> On Sep 1, 2020, at 5:11 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Jonathan Foulkes <jf@jonathanfoulkes.com> writes:
>
>> Thanks Toke, we currently are on an MT7621a @880, so a dual-core.
>
> Right, so some benefit might be possible here. Does the NIC have
> multiple hardware queues (`ls /sys/class/net/$IFACE/queues` should tell
> you)?
>
>> 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.
>
> Yup, the number of cores is only going to go up, so for CAKE to stay
> relevant it'll need to be able to take advantage of this eventually :)
>
> -Toke
[-- Attachment #2: Type: text/html, Size: 4629 bytes --]
next prev parent reply other threads:[~2020-09-02 20:26 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
2020-09-01 21:11 ` Toke Høiland-Jørgensen
2020-09-02 20:26 ` Jonathan Foulkes [this message]
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=99EE16A1-6CC9-4EB6-A6DC-CE2E910C6ADE@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