Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] [NetDev-People] 0x19: Talk, mq-cake: Scaling software rate limiting across CPU cores
Date: Mon, 10 Feb 2025 11:11:43 +0100	[thread overview]
Message-ID: <564C0719-2569-4A8A-981D-35F9473F8AF2@gmx.de> (raw)
In-Reply-To: <87bjvarvtd.fsf@toke.dk>

That sounds most excellent...

This also means that now we need cheap router hardware with > 2 NIC queues and > 2 CPUs ;) (with ingress and egress shaping the current state is that 2 CPUs can be utilised). I wonder, does this work for IFBs as well or only for real hardware NIC queues?

Regards
	Sebastian


> On 10. Feb 2025, at 10:30, Toke Høiland-Jørgensen via Cake <cake@lists.bufferbloat.net> wrote:
> 
> FYI :)
> 
> 
> From: Jamal Hadi Salim via people <people@netdevconf.info>
> Subject: [NetDev-People] 0x19: Talk, mq-cake: Scaling software rate limiting across CPU cores
> Date: 9. February 2025 at 14:37:41 CET
> To: people <people@netdevconf.info>
> Cc: Kimberley Jeffries <kimberleyjeffries@gmail.com>, Lael Santos <lael.santos@expertisesolutions.com.br>, program-committee@netdevconf.info, Bruno Banelli <bruno.banelli@sartura.hr>, j.koeppeler@tu-berlin.de, stefan.schmid@tu-berlin.de, Jamal Hadi Salim <jhs@mojatatu.com>
> 
> 
> Qdiscs rely on global lock to sync state across CPUs and therefore
> dont scale in presence of many cores (or in presence of very high
> bandwidth).
> Jonas Köppeler, Toke Høiland-Jørgensen, and Stefan Schmid implemented
> a multi-queue variant of sch_cake that can scale its rate limiting
> across hardware queues (and thus CPU cores) by sharing a bit of state
> on top of the mq qdisc.
> 
> In this talk, they will present the implementation, performance
> evaluation, as well as discuss their proposal for an API that will
> make this work upstreamable, and applicable to other qdiscs as well.
> 
> Details: https://netdevconf.info/0x19/16
> 
> cheers,
> jamal
> _______________________________________________
> people mailing list -- people@netdevconf.info
> To unsubscribe send an email to people-leave@netdevconf.info
> 
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  reply	other threads:[~2025-02-10 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM0EoM=bFMVMV-f2n4BNSJoqOAxqr+kcJ9kg2NLVvmw2rX-2WA@mail.gmail.com>
2025-02-10  9:30 ` [Cake] Fwd: " Toke Høiland-Jørgensen
2025-02-10 10:11   ` Sebastian Moeller [this message]
2025-02-10 10:35     ` [Cake] " Toke Høiland-Jørgensen
2025-02-10 12:06       ` Sebastian Moeller
2025-02-10 12:30         ` Toke Høiland-Jørgensen

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

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

  git send-email \
    --in-reply-to=564C0719-2569-4A8A-981D-35F9473F8AF2@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.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