Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>,
	jordan@inacomptc.com,  Jeff Hansen <x@jeffhansen.com>,
	contact@daryllswer.com
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] CAKE is going to be deployed on Alta Labs any day now!
Date: Fri, 21 Mar 2025 09:27:56 +0100	[thread overview]
Message-ID: <CAJUtOOj1+US-u-aB=8=dCFnoi1pCmzjojSUY-46mL7_Uq3fV8A@mail.gmail.com> (raw)
In-Reply-To: <7FBEC0CA-162E-48A2-81D6-97CDD2F63EEC@gmail.com>

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

Happy to see that! Thanks, guys.

Adding Jeff <https://www.linkedin.com/in/jeff-hansen-6794021/>, Alta Labs
CTO - Darryl <https://x.com/DaryllSwer/status/1902486684476047544> has a
suggestion how to push this further: "Maybe they can add both FQ_CoDel and
CAKE with BQL support? How's hardware-offloading of FQ_CoDel looking on
these “prosumer” equipment these days? I haven't kept up over a year on
this topic."

All the best,

Frank

Frantisek (Frank) Borsik



https://www.linkedin.com/in/frantisekborsik

Signal, Telegram, WhatsApp: +421919416714

iMessage, mobile: +420775230885

Skype: casioa5302ca

frantisek.borsik@gmail.com


On Fri, Mar 21, 2025 at 3:44 AM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 19 Mar, 2025, at 12:01 am, Frantisek Borsik via Cake <
> cake@lists.bufferbloat.net> wrote:
> >
> > Should be pushed through production in day or two and they will be
> talking about it on https://streamyard.com/watch/ubYm2AffWkYi this
> Wednesday,  March 19, at 1PM EST / 12PM CST / 11AM MST / 10AM PST
>
> I joined the stream, and was able to ask about the throughput they were
> getting with CAKE on their hardware.  This is just for the "Route 10"
> rather than their APs, and they reported getting about 2.5Gbps throughput
> with CAKE enabled. They do correctly note that the hardware-accelerated
> forwarding path is disabled for the interface where CAKE is turned on.
>
> Supporting 2.5Gbps is pretty good I think, and should be sufficient to
> handle all practical Internet subscriptions that are likely to require
> bufferbloat mitigation.  For comparison, on the same call they claimed
> about 800Mbps throughput for acting as a WireGuard tunnel endpoint.
>
>  - Jonathan Morton

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

  reply	other threads:[~2025-03-21  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 22:01 Frantisek Borsik
2025-03-21  0:31 ` jordan
2025-03-21  2:44 ` Jonathan Morton
2025-03-21  8:27   ` Frantisek Borsik [this message]
2025-03-24 15:23     ` Jeff Hansen
2025-03-24 15:39       ` Daryll Swer
2025-03-27 18:45         ` Frantisek Borsik

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='CAJUtOOj1+US-u-aB=8=dCFnoi1pCmzjojSUY-46mL7_Uq3fV8A@mail.gmail.com' \
    --to=frantisek.borsik@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=contact@daryllswer.com \
    --cc=jordan@inacomptc.com \
    --cc=x@jeffhansen.com \
    /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