iommu_alloc_pages_sz(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– iommu_alloc_pages_sz(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual β€” yes that's the manual name, we're fancy here β€” and today's main character is iommu_alloc_pages_sz, a little function that's out here handing you pages like it's Oprah. πŸŽ€


✨ NAME ✨

iommu_alloc_pages_sz β€” the way it allocates a zeroed page of a given size from a specific NUMA node. that's it, that's the whole vibe. ✨


🌸 SYNOPSIS 🌸

void * iommu_alloc_pages_sz (gfp_t gfp , size_t size );

literally just two arguments, no cap. look at her go 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • gfp β€” the buddy allocator flags, iykyk. this is you telling the allocator how you want the memory served. πŸ‘‘
  • size β€” the memory size to allocate, and heads up bestie, this is rounded up to a power of 2. so don't come crying to me if you asked for something weird and got a nicer number back. πŸ’…

🧚 DESCRIPTION 🧚

it returns the virtual address of the allocated page. that's the tea. you give it flags and a size, you get back a virtual address, periodt. πŸ’–


πŸ”₯ SEE ALSO πŸ”₯

like, go read them, they're all in the same friend group fr fr 🫢


ngl this one's short and sweet β€” no dangerous behaviour flagged in the source, no environment variables, no exit statuses, just vibes and a virtual address. πŸ’œ

mwah, that's a wrap! this page lives under ./drivers/iommu and it's dated October 2026, so mark your calendar bestie πŸ—“οΈπŸ’… β€” signed, sealed, delivered, and slaying βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from