ice_get_num_per_func(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ice_get_num_per_func β€” determine number of resources per PF. Straight out of the Kernel API Manual, bestie β€” this icon is here to do the resource-splitting math. ✨

✨ SYNOPSIS ✨

u32 ice_get_num_per_func (struct ice_hw *hw , u32 max );

πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW structure. It's giving hardware gossip central. 🫢
  • max β€” value to be evenly split between each PF. The big number getting divided up, no cap. πŸ’…

🌸 DESCRIPTION 🌸

Okay so here's the vibe: ice_get_num_per_func determines the number of valid functions by going through the bitmap returned from parsing capabilities. Then it uses that to calculate the number of resources per PF based on the max value passed in. Literally resource-splitting math with main character energy. 🧚

πŸ¦‹ SEE ALSO πŸ¦‹

The whole kernel friend group is linked here β€” Kernel file ./drivers/net/ethernet/intel/ice/ice_common.c and everyone below:


That's the whole page, bestie β€” sourced from ./drivers/net/ethernet/intel/ice, dated October 2026, and signing off with ice_get_num_per_func(9) energy. πŸ’…πŸ«Ά

πŸ“¦ where this page comes from