GPU_BUDDY_CLEAR_ALLOCATION(9)

💖 NAME 💖

GPU_BUDDY_CLEAR_ALLOCATION — bestie, it's giving "prefer pre-cleared (zeroed) memory" ✨

So like, this is the flag that says hey, hand me the clean stuff first 🧚

---

✨ SYNOPSIS ✨

GPU_BUDDY_CLEAR_ALLOCATION

That's it. That's the whole synopsis. No arguments, no parameters, no little extras — just the name and vibes 💅 (this page lives in the Kernel API Manual, section 9, iykyk 🎀)

---

🌸 DESCRIPTION 🌸

Okay so here's the tea ☕ — when you use this, the allocator will attempt to allocate from the clear tree first. Clean memory, zeroed memory, the good stuff 🫶

But if there's insufficient clear memory available, it falls back to dirty memory. No cap, that's the whole deal — it tries clean, and if clean is running low it settles for dirty instead of just giving up 😭

And when is this lowkey iconic? When the caller needs zeroed memory and wants to avoid GPU clear operations — you skip the whole extra clear step and just take memory that's already been pre-cleared. Efficiency, main character energy 👑🔥

⭐ vibe check: it's a preference, not a guarantee — the fallback to dirty memory is built right in, so don't come for it when it does exactly what the page says 🙈

---

🦋 SEE ALSO 🦋

Go read the whole friend group, fr fr 💜

• Kernel file ./include/linux/gpu_buddy.h
• GPU_BUDDY_RANGE_ALLOCATION(9)
• GPU_BUDDY_TOPDOWN_ALLOCATION(9)
• GPU_BUDDY_CONTIGUOUS_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)

---

slay, you made it to the end 🎀💖 This cutie lives in <pink>./include/linux</pink>, dated October 2026, and the manual is the Kernel API Manual — GPU_BUDDY_CLEAR_ALLOCATION(9), periodt 💅✨