nfp_flower_m...loaded_flows(9)

💅 nfp_flower_merge_offloaded_flows 💅

okay so bestie, this is a page from the Kernel API Manual — yes the actual kernel, not a vibe. it's about merging two offloaded flows into one, and honestly? it's giving ✨ efficiency ✨. let's get into it 🫶

---

🌸 NAME 🌸

nfp_flower_merge_offloaded_flows — merge 2 existing flows to single flow. that's it. that's the whole thing. two flows walk in, one flow walks out 😭💖

---

✨ SYNOPSIS ✨

int nfp_flower_merge_offloaded_flows (struct nfp_app *app , struct
nfp_fl_payload *sub_flow1 , struct nfp_fl_payload *sub_flow2 );

like, the whole function in one breath. iconic.

---

🎀 ARGUMENTS 🎀

• app — pointer to the APP handle. it's the main character of this whole operation fr fr 👑
• sub_flow1 — the initial flow that got matched and produced the merge hint. it's the one that starts the conversation 💬
• sub_flow2 — the post recirculation flow that got matched in the merge hint. the one that finishes it 🦋

---

🧚 DESCRIPTION 🧚

so what does it do? it combines 2 flows (if they're valid, no cap — validity check is real) into a single flow. the initial one gets removed from hw, and then the new merged flow gets offloaded. basically a glow-up transformation: out with the old, in with the merged 💅✨

lowkey important: the "if valid" part is doing heavy lifting there. not every flow pairing gets to slay. 🫶

---

🔥 RETURN 🔥

• negative value on error 😭
• 0 in success ⭐

so like, zero is the good one here. yes, zero = win. iykyk.

---

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/net/ethernet/netronome/nfp/flower/offload.c
• nfp_flower_validate_pre_tun_rule(9)
• nfp_flower_add_offload(9)
• nfp_flower_del_offload(9)
• nfp_flower_get_stats(9)

go read those too bestie, they're the friend group 🫶

---

and that's the whole page!! this one's from ./drivers/net/ethernet/netrono..., dated October 2026 — go off kernel docs, you ate that 💖🎀🧚‍♀️