General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davecb.42@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU)
Date: Thu, 3 Sep 2020 18:14:49 -0400	[thread overview]
Message-ID: <8c4212c4-3acb-6616-d9a2-6bef7e65bbad@rogers.com> (raw)
In-Reply-To: <877dtbgcc6.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On 2020-09-03 10:32 a.m., Toke Høiland-Jørgensen via Bloat wrote

> Yeah, offloading of some sort is another option, but I consider that
> outside of the "CAKE stays relevant" territory, since that will most
> likely involve an entirely programmable packet scheduler. There was some
> discussion of adding such a qdisc to Linux at LPC[0]. The Eiffel[1]
> algorithm seems promising.
>
> -Toke

I'm wondering if edge servers with 1Gb NICs are inside the "CAKE stays 
relevant" territory?

My main customer/employer has a gazillion of those, currently reporting

**

*qdisc mq 0: root*

*

qdisc pfifo_fast 0: parent :8 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 
1 1 1

...

*

because their OS is just a tiny bit elderly (;-)). We we're planning to 
roll forward this quarter to centos 8.2, where CAKE is an option.

It strikes me that the self-tuning capacity of CAKE might be valuable 
for a whole /class/ of small rack-mounted machines, but you just 
mentioned the desire for better multi-processor support.

Am I reaching for the moon, or is this something within reach?

--dave

-- 

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


[-- Attachment #2: Type: text/html, Size: 3003 bytes --]

  parent reply	other threads:[~2020-09-03 22:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 17:27 [Bloat] CAKE in openwrt high CPU 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
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                 ` David Collier-Brown [this message]
2020-09-04  1:19                   ` [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU) 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=8c4212c4-3acb-6616-d9a2-6bef7e65bbad@rogers.com \
    --to=davecb.42@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    --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