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] flow dissection vs encapsulated traffic?
Date: Sun, 5 Feb 2023 13:44:16 -0800	[thread overview]
Message-ID: <CAA93jw4+kMLHoOSE9xLhxcHcmoSj4HMBEotW_JgpOkrb046Skw@mail.gmail.com> (raw)

In looking how the code has morphed since I last looked at it, I found
myself staring at this bit...

        skb_flow_dissect_flow_keys(skb, &keys,
                                   FLOW_DISSECTOR_F_STOP_AT_FLOW_LABEL);

// so we have delved deeply into the packet at this point... finding
various encapsulations...

then we get to:

        /* Don't use the SKB hash if we change the lookup keys from conntrack */
        if (nat_enabled && cake_update_flowkeys(&keys, skb))
                use_skbhash = false;

This leverages skb_protocol(), which as best as I can tell just peers
into the *vlan headers*,
not deeper into the packet...

Then we proceed merrily into the update_flowkeys code thinking it is
the outer type
(ipv4), not the inner, then dissect away, using a v4 union...

Am I reading this wrong? Please tell me I am reading this wrong...




-- 
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC

             reply	other threads:[~2023-02-05 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 21:44 Dave Taht [this message]
2023-02-05 22:17 ` 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=CAA93jw4+kMLHoOSE9xLhxcHcmoSj4HMBEotW_JgpOkrb046Skw@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