ice_get_itr_intrl_gran(9)

📦 version 7.3.1, in nixpkgs unstable

✨ ice_get_itr_intrl_gran(9) ✨

okay so bestie, welcome to the manual page for ice_get_itr_intrl_gran — yes that's a whole lot of letters, yes you're gonna say it out loud like five times before it rolls off the tongue 💅 and yes, this is the kernel API manual (section 9, iykyk), so buckle up 🎀

quick heads up: the official NAME line is literally just the function name, a dash, and then nothing. no description. no summary. just vibes. she said "my name is enough" and honestly? main character energy 👑

🌸 SYNOPSIS 🌸

void ice_get_itr_intrl_gran (struct ice_hw *hw );

that's it. that's the whole signature. no return value, no drama, just void and a pointer 🦋

💖 ARGUMENTS 💖

  • hw — pointer to the HW struct. that's the hardware struct, bestie, the one holding all the device tea 🫖

✨ DESCRIPTION ✨

so here's what she actually does 🧚

ice_get_itr_intrl_gran determines the ITR/INTRL granularities based on the maximum aggregate bandwidth according to the device's configuration during power-on.

read that again: the granularities get figured out from the max aggregate bandwidth, and that bandwidth comes from however the device was configured when it powered on. it's giving "i've known who i am since boot" 💀✨ no cap.

🔥 SEE ALSO 🔥

  • Kernel file ./drivers/net/ethernet/intel/ice/ice_common.c

and now the friend group, because this function literally knows everyone 👑 apparently the whole ice family shows up to the party, so here's the full guest list, in order, no one left out 🫶

like. that's the whole group chat. every single one. we love a function with a social life 🌈⭐

and that's the page, bestie 🫶 shoutout to the source <pink>./drivers/net/ethernet/intel/ice</pink> and the date <purple>October 2026</purple> — this manual page for ice_get_itr_intrl_gran(9) was served fresh from the kernel API manual, and she ate 💅 periodt 💖

📦 where this page comes from