dmam_pool_create(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dmam_pool_create(9) 💅

okay so this is a page straight out of the Kernel API Manual bestie, and it's about dmam_pool_create — the managed glow-up of dma_pool_create(). yes ma'am, it's giving "I handle the cleanup so you don't have to" ✨

🌸 NAME 🌸

dmam_pool_create — the managed version of dma_pool_create(). literally the same vibe but it cleans up after itself 🫶

🎀 SYNOPSIS 🎀

struct dma_pool * dmam_pool_create (const char *name , struct device
       *dev , size_t size , size_t align , size_t allocation );

🦋 ARGUMENTS 🦋

  • name — the pool's name, bestie. it's for diagnostics, so pick something cute and identifiable 💖
  • dev — the device that's gonna be doing the DMA. the main character of this whole story fr fr 👑
  • size — how big the blocks in this pool are 🔥
  • align — the alignment requirement for the blocks; must be a power of two, no cap, that's a hard rule 😭
  • allocation — returned blocks won't cross this boundary (or zero, if you're feeling boundary-less) ⭐

💜 DESCRIPTION 💜

So this is the managed dma_pool_create. The DMA pool you make with this function is automatically destroyed on driver detach — like, you don't even have to ask, it just handles it. main character energy but make it responsible 💅

🌈 RETURN 🌈

You get back a managed DMA allocation pool with all the requested characteristics you asked for... or NULL if one can't be created. sad but true 🙈

✨ SEE ALSO ✨

not me dropping the whole friend group 💀 — you already know the source lives in the Kernel file ./mm/dmapool.c, and the squad is:

🫶 that's the whole page bestie, go forth and pool responsibly 🫶

kisses from ./mm — this one's dated October 2026, and yes, it's dmam_pool_create(9) out of 9, slay 🎀💖✨

📦 where this page comes from