From: Stephen Hemminger <stephen@networkplumber.org>
To: Jan Rovner via Cake <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake - flow (or host) weight request - how to implement
Date: Wed, 27 Sep 2023 13:27:32 -0700 [thread overview]
Message-ID: <20230927132732.6585172a@hermes.local> (raw)
In-Reply-To: <e6464f0d9e7e4c91b26f2d08d72b1a0c@diadema.cz>
On Wed, 27 Sep 2023 17:48:06 +0000
Jan Rovner via Cake <cake@lists.bufferbloat.net> wrote:
> Hello,
>
> I am trying to experiment with sch_cake.c, my goal is to ad-hoc prioritize / deprioritize traffic served to specified a host(s). The prioritization would be controlled by an external system and it should handle well the situation where a host has active flow(s).
Is it possible to use one or more existing BPF hooks to change DCSP bits for that paths you wish to adjust.
The point is that changes to upstream base code are hard to maintain, and that is what BPF initial hooks
were meant to provide.
next prev parent reply other threads:[~2023-09-27 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 17:48 Jan Rovner
2023-09-27 20:27 ` Stephen Hemminger [this message]
2023-09-27 20:44 ` Sebastian Moeller
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=20230927132732.6585172a@hermes.local \
--to=stephen@networkplumber.org \
--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