ixgbe_get_num_per_func(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 ixgbe_get_num_per_func (9) — Kernel API Manual ✨

okay bestie, welcome to the <pink>ixgbe_get_num_per_func(9)</pink> page 💅 this is a lil kernel API manual from the Kernel API Manual, and it's genuinely not scary, i promise 🫶

✨ NAME ✨

ixgbe_get_num_per_func — figure out how many resources each PF gets, no cap 🎀

💖 SYNOPSIS 💖

u32 ixgbe_get_num_per_func (struct ixgbe_hw *hw , u32 max );

like, that's the whole vibe-check signature bestie, she's a u32 and she takes two args ✨

🦋 ARGUMENTS 🦋

  • hw — a pointer to the HW structure 👑 literally the hardware info handoff.
  • max — the value that's gonna get split evenly between each PF 🍓 even-steven, periodt.

🌈 DESCRIPTION 🌈

so here's what's happening 💫 this function determines the number of valid functions by walking through the bitmap that comes back from parsing capabilities — and then it uses that to calculate the number of resources per PF, based on the max value you passed in ✨

tl;dr: bitmap → valid function count → divide max up per PF. it's giving math but make it firmware 🧚

🔥 RETURN 🔥

it hands you back the number of resources per PF 💖 … or 0 if there are no PFs available 😭 (yes, zero. not a vibe, but it's honest.)

⭐ SEE ALSO ⭐

lowkey the biggest friend group in the kernel, ngl 🫶 the kernel file lives at ./drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c and these are all her besties:

reminder bestie: max gets split evenly between every PF, and if there are no PF besties to share with, you get 0. no PFs, no resources, no drama 🫶

and that's the whole page, ily 💜 this came from <lavender>./drivers/net/ethernet/intel/i...</lavender> and it's dated October 2026 🗓️✨ mwah, go read some more ixgbe pages, they're iconic 👑🌈

📦 where this page comes from