efx_tc_mangle(9)

💅 efx_tc_mangle — bestie's guide to handling a single 32-bit (or less) pedit 🎀

okay so real talk, this is a page from the Kernel API Manual and it's all about one lil' function that handles exactly one pedit — and by "one" we mean 32-bit or less, no cap. let's get into it ✨

---

🌸 SYNOPSIS 🌸

int efx_tc_mangle (struct efx_nic *efx , struct efx_tc_action_set *act ,
const struct flow_action_entry *fa , struct efx_tc_mangler_state *mung ,
struct netlink_ext_ack *extack , struct efx_tc_match *match );

it's giving six-parameter main character energy, and honestly? iconic. 🌈

---

💖 ARGUMENTS 💖

• efx — the NIC we're installing a flow rule on 🫶 (yes, the actual hardware, we're being brave today)
• act — the action set (cursor) to update ✨ this is the thing that gets moved along
• fa — the FLOW_ACTION_MANGLE action metadata 🎀 the vibes, the details, the lore
• mung — accumulator for partial mangles 🦋 lowkey a little bucket where half-finished mangles chill
• extack — netlink extended ack for reporting errors 💀 because when things go wrong we like details
• match — original match used along with the mangle action 👑 the context, the receipts, the origin story

---

🔥 DESCRIPTION 🔥

so basically: this function identifies the fields written by a FLOW_ACTION_MANGLE, and then records the partial mangle state in mung. 🍓

and here's the slay part — if this mangle completes an earlier partial mangle, it consumes and applies it to act by calling efx_tc_complete_mac_mangle. 😭 like, the two halves finally meet and it's beautiful. periodt. 💅

ngl, this is the kind of function that does one thing and does it well. no notes. 🧚

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/net/ethernet/sfc/tc.c — TC conntrack sequences(9) 📁
• struct efx_tc_mangler_state(9) 💜
• efx_tc_incomplete_mangle(9) ⭐

---

and that's the whole vibe check! 🎀 this page came to you straight from ./drivers/net/ethernet/sfc, dated October 2026 — go forth and mangle responsibly, bestie 💖✨🦋