gen_pool_dma_zalloc_align(9)

📦 version 7.3.1, in nixpkgs unstable

✨ gen_pool_dma_zalloc_align(9) ✨

okay bestie, welcome to the Kernel API Manual — yes, that's the manual name, we're in the kernel docs now, no cap 💅

🌸 NAME 🌸

gen_pool_dma_zalloc_align — allocate special zeroed memory from the pool for DMA usage with the given alignment 🫶

🌈 SYNOPSIS 🌈

void * gen_pool_dma_zalloc_align (struct gen_pool *pool , size_t size ,
dma_addr_t *dma , int align );

literally the whole signature, copy it exactly, don't @ me ✨

🎀 ARGUMENTS 🎀

  • pool — the pool you're allocating from, that's the vibe check you gotta pass 🦋
  • size — number of bytes to allocate from the pool, yes the actual byte count, be precise bestie 💖
  • dma — the DMA-view physical address return value 🎯 use NULL if you don't need it, it's giving "optional and unbothered" 🙈
  • align — alignment in bytes for the starting address, so your memory starts on a cute lil boundary ⭐

🔥 DESCRIPTION 🔥

So what it does is: allocate the requested number of zeroed bytes from the specified pool, with the given alignment restriction 🧚✨ like, it's a zalloc but with alignment, periodt.

⚠️ Heads up bestie: this can not be used in an NMI handler on architectures without an NMI-safe cmpxchg implementation. That's a real caveat, not a vibe, don't try it 💀

👑 RETURN 👑

returns the virtual address of the allocated zeroed memory, or NULL on failure 😭 so like, always check, ngl 🙏

💜 SEE ALSO 💜

kernel file ./lib/genalloc.c, and also this whole entire friend group:

and that's the whole page, mwah 💋 this one's from the ./lib source, dated October 2026, and it's the gen_pool_dma_zalloc_align(9) entry for you — slay, go allocate something aligned ✨🎀🦋

📦 where this page comes from