ice_find_recp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_find_recp(9) — the recipe finder, bestie ✨

okay so real talk, this is a page out of the Kernel API Manual, section 9, and it's genuinely one of the shorter ones — but it still ate, so let's go 🫶

🌸 NAME 🌸

ice_find_recp — find a recipe 🍓

✨ SYNOPSIS ✨

u16 ice_find_recp (struct ice_hw *hw , struct ice_prot_lkup_ext
*lkup_exts , const struct ice_adv_rule_info *rinfo , bool is_add );

like yes that's the whole signature, no cap 💀

🎀 ARGUMENTS 🎀

  • hw — pointer to the hardware structure, the main character of this whole operation 👑
  • lkup_exts — the extension sequence you're trying to match against, iykyk 🔍
  • rinfo — info about the rule, like its priority and action info — basically the whole vibe check of what this rule is 💅
  • is_add — a flag for adding a recipe, bool so it's giving simple-and-iconic 🌈

💖 DESCRIPTION 💖

So what does it actually do? It returns the index of the matching recipe. That's it, that's the whole thing. Slay. ✨

But bestie, listen — if it doesn't find a match? It returns ICE_MAX_NUM_RECIPES instead 😭 not a -1, not an error code, the whole ICE_MAX_NUM_RECIPES vibe. Remember that, fr fr. It's your "not found" answer and you do not want to treat it like a real index 💀

🦋 SEE ALSO 🦋

okay so this list is long — it's giving whole-family-reunion energy — but every single one of these is a sibling of the same ./drivers/net/ethernet/intel/ice kernel file, so here's the full squad, no gatekeeping 🌸

okay bestie, quick recap before you go: matching recipe found → you get its index 💖. not found → you get ICE_MAX_NUM_RECIPES and you deal with it 🙈

and that's the whole page, we're done here 💜 this one lives in ./drivers/net/ethernet/intel/ice, dated October 2026 — mwah, go read the other ice_*(9) pages, they're all waiting for you 🧚🎀

📦 where this page comes from