Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Sebastian Moeller" <moeller0@gmx.de>,
	"Joel Wirāmu Pauling" <joel@aenertia.net>
Cc: Cake List <cake@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	Jonathan Morton <chromatix99@gmail.com>
Subject: Re: [Cerowrt-devel] 10gige and 2.5gige
Date: Fri, 17 Dec 2021 12:33:08 +0100	[thread overview]
Message-ID: <874k77cvpn.fsf@toke.dk> (raw)
In-Reply-To: <D1CBC326-1ABB-4636-8B83-AE5970277200@gmx.de>

Sebastian Moeller <moeller0@gmx.de> writes:

> Mmmh, I guess our approach at traffic shaping does not scale well at those speeds. Maybe this could be fixed with larger batching?
>
> I think it might be worth trying to switch to simple.qos/fq_codel and
> set a somewhat larger burst/quantum duration in defaults.sh, then
> disable BQL on the NIC and configure a beefy txqueuelen on the
> interface. This might help making SQM limp along to higher rates. If
> that would actually work, we could try to see whether we can make cake
> learn coarser batching ("bursts" and/or quantum) at high rates (but I
> did not check what cake does internally, it might already do this,
> @jonathan?)....

I fear the problem is rather the lack of multithreading. I have a fairly
beefy 8-core ARM box for my main router these days, and even that can't
forward at a gigabit on a single core. There was a bug in the HW
configuration so all traffic was sent to a single core, which resulted
in 50+ms of bloat and traffic capping out way short of a gigabit. Now
that it's fixed and traffic is mixed over all eight cores I have smooth
sailing and no bloat. Thankfully I don't need to shape, so I'm just
running straight mq+fq_codel on the physical interface....

-Toke

  reply	other threads:[~2021-12-17 11:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 16:20 Dave Taht
2021-12-16 18:16 ` David P. Reed
2021-12-16 19:31   ` Joel Wirāmu Pauling
2021-12-16 21:29     ` David P. Reed
2021-12-16 21:43       ` David Lang
2021-12-16 21:57         ` Joel Wirāmu Pauling
2021-12-17  8:18           ` Sebastian Moeller
2021-12-17  8:36             ` Joel Wirāmu Pauling
2021-12-17  8:39               ` Joel Wirāmu Pauling
2021-12-17  9:26                 ` Sebastian Moeller
2021-12-17 11:33                   ` Toke Høiland-Jørgensen [this message]
2021-12-17  8:57               ` Sebastian Moeller
2021-12-19 18:07             ` David P. Reed
2021-12-23  1:17               ` Aaron Wood

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=874k77cvpn.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=joel@aenertia.net \
    --cc=moeller0@gmx.de \
    /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