alloc_iova(9)

📦 version 7.3.1, in nixpkgs unstable

💅 alloc_iova — the Kernel API Manual tea ☕✨

okay bestie, welcome to the alloc_iova(9) page, brought to you by the Kernel API Manual, and honestly? it's giving "small function, big responsibilities." let's get into it 🫶

✨ NAME ✨

alloc_iova — literally just allocates an iova. that's the whole vibe. no cap. 🎀

🌸 SYNOPSIS 🌸

struct iova * alloc_iova (struct iova_domain *iovad , unsigned long size
, unsigned long limit_pfn , bool size_aligned );

like, copy that exactly, bestie, don't freestyle it 💀

🦋 ARGUMENTS 🦋

  • iovad — the iova domain in question. yes, that one. the domain we're doing all this in 💖
  • size — how many page frames you wanna allocate. the size. the amount. you get it ✨
  • limit_pfn — the max limit address. the ceiling. the "don't go past this" line 🔥
  • size_aligned — set this if you need a size_aligned address range, iykyk

and here's the lore, bestie 👑 — this function allocates an iova in the range iovad->start_pfn to limit_pfn, searching top-down from limit_pfn to iovad->start_pfn. top-down, not bottom-up, don't get it twisted 🙈

and if the size_aligned flag is set, then the allocated address iova->pfn_lo will be naturally aligned on roundup_power_of_two(size). naturally aligned!! we love a tidy address 🌈⭐

💜 SEE ALSO 💜

go read them, they're all in the group chat too, fr fr 💅

lowkey reminder: size_aligned only does its alignment thing when you actually set it, so set it if you need it, bestie. the flag isn't decorative 🎀

and that's the page!! sign-off time: this one's from ./drivers/iommu, dated October 2026 — put it in your calendar, screenshot it, whatever 😭💖 mwah, slay, go allocate responsibly 🧚‍♀️💅

📦 where this page comes from