pcpu_balance_populated(9)

📦 version 7.3.1, in nixpkgs unstable

👑 pcpu_balance_populated — Kernel API Manual, bestie edition ✨

Okay so listen, this page is pcpu_balance_populated(9) from the Kernel API Manual and honestly she's a whole vibe. Let's get into it 💅

🌸 NAME 🌸

pcpu_balance_populated — manage the amount of populated pages, no cap

🦋 SYNOPSIS 🦋

void pcpu_balance_populated (void );

That's it. That's the whole signature. Short and iconic, as she should be 💖

🎀 ARGUMENTS 🎀

  • void — no arguments, bestie. She takes nothing, she gives everything. Zero notes, main character energy fr fr 🫶

⭐ DESCRIPTION ⭐

So the whole point of this function is to maintain a certain amount of populated pages so that atomic allocations can actually be satisfied. Like, she's out here keeping the vibes stocked so nobody's request gets left on read 🙈

But here's the part where you gotta be careful, okay? It is possible that this is called when physical memory is scarce — and that will cause the OOM killer to be triggered 😭 And ngl, we should avoid doing so until an actual allocation causes the failure, because it is possible that requests can be serviced from already backed regions. Basically: don't let the panic set in before it's actually the moment, iykyk 🧚

⚠️ Real talk: this can be called when physical memory is scarce, and that can trigger the OOM killer. Avoid that until an actual allocation causes the failure, since requests can be serviced from already backed regions. She's dramatic but the caveat is real 💀

🔥 CONTEXT 🔥

  • pcpu_lock — and yes she can be dropped temporarily, so don't be weird about it ✨

🌈 SEE ALSO 🌈

Kernel file ./mm/percpu.c, plus the whole squad, all of them, every single one 👑:

Like, the entire percpu friend group showed up to the function. Obsessed 💜

Anyway bestie, this page lives in ./mm and it's dated October 2026, and the whole thing answers to pcpu_balance_populated(9). Slay, stay hydrated, and mind your populated pages 💅✨🍓

📦 where this page comes from