Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] cakemq V further thoughts
Date: Sun, 27 Aug 2023 18:36:18 -0700	[thread overview]
Message-ID: <CAA93jw45oM1ARuZootGE8O-tybg-bqdKZEmU8YCEu8Hf2XPW0g@mail.gmail.com> (raw)

I continue to revise and edit this piece.

https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit

Today I came up with two other possible objectives to tackle, so
instead of re-re-re-re-rereading the above, they are:

BANG mode - there are certain cases where it it known that the
bandwidth is going to drop significantly (examples include a cnwave to
5ghz backup transition and Starlinks’15s update cycle) where it makes
sense to drop a bunch of packets immediately rather than wait for the
shift to gradually be seen.

tc qdisc change dev eth0 root cake bandwidth <newbandwidth> bang

Cake-autorate rework - the first attempt at doing this directly in
cake frankly… does not work well. There has been a lot of innovation
in the sqm-autorate and cake-autorate projects, which live in
userspace today that might be applied more directly. BANG mode, above,
is an untried inspiration to cake autorate, and would also cope with
L4S flows by doing drops on big rate changes, rather than marks.


-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

                 reply	other threads:[~2023-08-28  1:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw45oM1ARuZootGE8O-tybg-bqdKZEmU8YCEu8Hf2XPW0g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /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