From: Jonathan Morton <chromatix99@gmail.com>
To: "Holland, Jake" <jholland@akamai.com>
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Congestion control with FQ-Codel/Cake with Multicast?
Date: Sat, 25 May 2024 14:15:32 +0300 [thread overview]
Message-ID: <1DA90C88-5762-43C4-84FF-51F4623D82CE@gmail.com> (raw)
In-Reply-To: <A7CFFD21-1EF5-48A0-92AC-A62D9C589489@akamai.com>
> On 24 May, 2024, at 12:43 am, Holland, Jake via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> I agree with your conclusion that FQ systems would see different
> streams as separate queues and each one could be independently
> overloaded, which is among the reasons I don't think FQ can be
> viewed as a solution here (though as a mitigation for the damage
> I'd expect it's a good thing to have in place).
Cake has the facility to override the built-in flow and tin classification using custom filter rules. Look in the tc-cake manpage under "OVERRIDING CLASSIFICATION". This could be applicable to multicast traffic in two ways:
1: Assign all traffic with a multicast-range IP address to the Video tin. Since Cake schedules by tin first, and only then by host and/or flow, this should successfully keep multicast traffic from obliterating best-effort and Voice tin traffic.
2: Assign all multicast traffic to a single flow ID (eg. zero), without reassigning the tin. This will cause it all to be treated like a single flow, giving the FQ mechanisms something to bite on.
- Jonathan Morton
next prev parent reply other threads:[~2024-05-25 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 14:56 Linus Lüssing
2024-05-21 15:25 ` Linus Lüssing
2024-05-23 21:43 ` Holland, Jake
2024-05-23 23:15 ` Holland, Jake
2024-05-25 11:15 ` Jonathan Morton [this message]
2024-05-24 13:58 ` 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/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=1DA90C88-5762-43C4-84FF-51F4623D82CE@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jholland@akamai.com \
--cc=linus.luessing@c0d3.blue \
/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