ice_get_irq_res(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ice_get_irq_res(9) β€” Kernel API Manual, bestie edition πŸ’–

okay so welcome to ice_get_irq_res(9), a genuine little kernel API manual page for the ice driver fam, and yes I'm gonna walk you through it like we're texting at 2am 🫢


✨ NAME ✨

ice_get_irq_res β€” get an interrupt resource. that's it, that's the whole name, and honestly? iconic. πŸ‘‘


🌸 SYNOPSIS 🌸

struct ice_irq_entry * ice_get_irq_res (struct ice_pf *pf , bool
       dyn_allowed );

look at her. two args, one return, zero drama. copy it exactly, no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • pf β€” the board private structure. like, the driver's own little private stash of board info, yk? πŸ¦‹
  • dyn_allowed β€” a bool that says whether this entry is allowed to be dynamically allocated. so like, yes-alloc or no-alloc energy πŸ™ˆ

⭐ DESCRIPTION ⭐

so what does she do. she allocates a new irq entry in the free slot of the tracker. simple as that, main character behaviour ✨

and because xarray is used here, she always allocates the new entry at the lowest possible index. always. lowest. possible. index. the way that xarray just does that? obsessed 😭

she also sets the proper allocation limit for the maximum tracker entries β€” so the cap on the tracker gets set correctly, no vibes-based limits happening here fr fr 🧚

Returns the allocated irq entry, or NULL on failure. if it flops, you get NULL, and that's the whole story πŸ’€

lowkey important: NULL on failure is the only failure signal she gives you. check it. periodt.

🌈 SEE ALSO 🌈

the whole friend group, all linked up, we love a connected cast 🫢✨


and that's the page!! sign-off time: this one lives in ./drivers/net/ethernet/intel/ice, dated October 2026, and it's ice_get_irq_res(9) β€” slay, bye bestie πŸ’…πŸŽ€πŸ”₯

πŸ“¦ where this page comes from