gen_pool_dma_alloc_algo(9)

📦 version 7.3.1, in nixpkgs unstable

Okay bestie, this is the manual page for gen_pool_dma_alloc_algo(9) from the Kernel API Manual. It’s giving “special pool memory, but make it DMA,” and honestly? Iconic. 🎀

✨ NAME ✨

gen_pool_dma_alloc_algo — allocate special memory from the pool for DMA usage with the given pool algorithm. Periodt. 💅

🌸 SYNOPSIS 🌸

void * gen_pool_dma_alloc_algo (struct gen_pool *pool , size_t size ,
dma_addr_t *dma , genpool_algo_t algo , void *data );

💖 ARGUMENTS 💖

  • pool — the pool to allocate from. 🫶
  • size — number of bytes to allocate from the pool.
  • dma — DMA-view physical address return value. Use NULL if unneeded.
  • algo — algorithm passed from caller.
  • data — data passed to algorithm.

🦋 DESCRIPTION 🦋

Okay so the actual job: allocate the requested number of bytes from the specified pool. ✨ It uses the given pool allocation function. Simple, clean, lowkey slay.

🚨 But bestie, can not be used in NMI handler on architectures without an NMI-safe cmpxchg implementation. That’s a hard no, not a vibe. 💀

⭐ RETURN ⭐

The return value is the virtual address of the allocated memory, or NULL on failure. That’s the whole tea. 🫶

🌈 SEE ALSO 🌈

Kernel file: ./lib/genalloc.c

The whole genpool friend group, fr fr:

Source/version: ./lib · Date: October 2026 · Page: gen_pool_dma_alloc_algo(9) — bye bestie, stay iconic 💅✨

📦 where this page comes from