GPU_BUDDY_C...S_ALLOCATION(9)

💅 GPU_BUDDY_C...S_ALLOCATION(9) — a.k.a. the "no gaps, bestie" flag 🎀

okay so real talk, this page lives in the Kernel API Manual (very official, very demure ✨) and it's about one lil flag from the GPU buddy allocator that has opinions about where your memory goes. buckle up 🦋

---

✨ NAME ✨

GPU_BUDDY_CONTIGUOUS_ALLOCATION — literally "Require physically contiguous blocks" 🫶 like it says it right there in the name, no cap

---

🌸 SYNOPSIS 🌸

GPU_BUDDY_CONTIGUOUS_ALLOCATION

that's it. that's the whole thing. it's a flag, not a function, she's lowkey minimal 💅

---

🔥 DESCRIPTION 🔥

okay so here's the vibe check 👑 — the allocation must be satisfied with a single contiguous block. one block. no pieces, no fragments, no "we'll figure it out later." it's giving main character energy and she refuses to be split up 💀

and if the requested size cannot be allocated contiguously? bestie, it just fails. dramatic? maybe. but the failure comes back as -ENOSPC and that's the whole story 🙈

ngl it's not mean about it, it's just honest — contiguous or nothing 💖

---

🦋 SEE ALSO 🦋

• kernel file ./include/linux/gpu_buddy.h — the home base, go say hi 🏠
• GPU_BUDDY_RANGE_ALLOCATION(9)
• GPU_BUDDY_TOPDOWN_ALLOCATION(9)
• GPU_BUDDY_CLEAR_ALLOCATION(9)
• GPU_BUDDY_CLEARED(9)
• GPU_BUDDY_TRIM_DISABLE(9)
• struct gpu_buddy_block(9)
• struct gpu_buddy(9)
• gpu_buddy_driver_set_lock(9)
• gpu_buddy_driver_lock_held(9)

like, the whole friend group honestly — go read all of them, iykwim 💜

---

and that's the page!! ⭐ she's short and sweet and she knows exactly what she wants.

sign-off time 🎀 — this lil icon came from ./include/linux and she's dated October 2026, so mark your calendars bestie 🍓💖 mwah, go allocate something contiguous 💅✨