Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Matt Corallo <cltaapptfwbs@mattcorallo.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Parsing DSCP out of skb->priority
Date: Sun, 7 Sep 2025 08:40:05 -0400	[thread overview]
Message-ID: <78318be7-30d0-4f6a-80f3-063f4558b142@mattcorallo.com> (raw)

Its (presumably) not uncommon to have multiple encapsulation tunnels running on a host which then 
wants to do (cake) shaping on the actual outbound interface. In this case, the skb->hash is 
(hopefully) preserved from the original packet to select the right flow queue, but the DSCP isn't. 
This is ideally what the priority field of the skb is for - `skbedit` can set the priority flag of 
the packet before "exiting" the tunnel interface, and cake can ultimately read that priority flag to 
select a tin. However, doing so requires manual tin mapping in skbedit, reading the DSCP field and 
mapping them to the right tin entirely be hand.

skbedit also supports `inheritdsfield` which just sets skb->priority to the DSCP field as-is. It 
would be nice if cake could read such priority fields, treating skb->priority as a DSCP when 
TC_H_MAJ(skb->priority) is zero (which it always will be in this case). Is there any interest in a 
patch to do so? Would such a patch need a new userspace option to disable it, or would wash suffice?

             reply	other threads:[~2025-09-07 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 12:40 Matt Corallo [this message]
2025-09-09 10:32 ` [Cake] " 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=78318be7-30d0-4f6a-80f3-063f4558b142@mattcorallo.com \
    --to=cltaapptfwbs@mattcorallo.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