pci_iov_vf_bar_get_sizes(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pci_iov_vf_bar_get_sizes — a Kernel API Manual moment

okay so bestie, welcome to the pci_iov_vf_bar_get_sizes(9) page ✨ this is the Kernel API Manual and we're literally about to make VF BAR sizes make sense, no cap 🎀

🌸 NAME 🌸

pci_iov_vf_bar_get_sizes — get VF BAR sizes allowing to create up to num_vfs 🫶

like, it tells you which VF BAR sizes you can work with so you can spin up as many as num_vfs VFs, periodt 💅

✨ SYNOPSIS ✨

u32 pci_iov_vf_bar_get_sizes (struct pci_dev *dev , int resno , int
num_vfs );

one function, three args, that's the whole vibe 💖

🦋 ARGUMENTS 🦋

  • dev — the PCI device 👑
  • resno — the resource number 🔢
  • num_vfs — number of VFs 🌈

💜 DESCRIPTION 💜

Get the sizes of a VF resizable BAR that can accommodate num_vfs within the currently assigned size of the resource resno. 🧚

translation: it looks at the size resno is rockin' right now and tells you which resizable BAR sizes are big enough to fit num_vfs in there. iconic behavior honestly 💅

⭐ RETURN ⭐

A bitmask of sizes in format defined in the spec (bit 0=1MB, bit 31=128TB). 🔥

so like, bit 0 = 1MB and bit 31 = 128TB, that's the spec's format, not mine, iykyk 🎀

🌈 SEE ALSO 🌈

Kernel file ./drivers/pci/iov.c plus the whole friend group:

💀 reminder bestie: this page is from ./drivers/pci, dated October 2026, and it's filed under pci_iov_vf_bar_get_sizes(9) — go read the whole squad, they all ate 💅✨🫶
📦 where this page comes from