From: Jonathan Morton <chromatix99@gmail.com>
To: davecb@spamcop.net
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU)
Date: Fri, 4 Sep 2020 04:19:41 +0300 [thread overview]
Message-ID: <8AA690BF-B027-420B-81B1-8E9F445D5BB7@gmail.com> (raw)
In-Reply-To: <8c4212c4-3acb-6616-d9a2-6bef7e65bbad@rogers.com>
> On 4 Sep, 2020, at 1:14 am, David Collier-Brown <davecb.42@gmail.com> wrote:
>
> I'm wondering if edge servers with 1Gb NICs are inside the "CAKE stays relevant" territory?
Edge servers usually have strong enough CPUs and I/O - by which I mean anything from AMD K8 and Intel Core 2 onwards with PCIe attached NICs - to run Cake at 1Gbps without needing special measures. I should run a test to see how much I can shove through an AMD Bobcat these days - not exactly a speed demon.
We're usually seeing problems with the smaller-scale CPUs found in CPE SoCs, which are very much geared to take advantage of hardware accelerated packet forwarding. I think in some cases there might actually be insufficient internal I/O bandwidth to get 1Gbps out of the NIC, into the CPU, and back out to the NIC again, only through the dedicated forwarding path. That could manifest itself as a lot of kernel time spent waiting for the hardware, and can only really be solved by redesigning the hardware.
- Jonathan Morton
next prev parent reply other threads:[~2020-09-04 1:19 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 ` [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU) David Collier-Brown
2020-09-04 1:19 ` Jonathan Morton [this message]
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=8AA690BF-B027-420B-81B1-8E9F445D5BB7@gmail.com \
--to=chromatix99@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