memblock_phys_alloc_range(9)

📦 version 7.3.1, in nixpkgs unstable

💅 memblock_phys_alloc_range(9) — Kernel API Manual, bestie edition ✨

okay so this is a page straight out of the Kernel API Manual, and it's about memblock_phys_alloc_range — a function that literally goes "here's a chunk of physical memory, but like… only inside this specific range, mwah 💋". no cap, it's giving "picky real-estate agent energy" and honestly? obsessed. 🎀

✨ NAME ✨

memblock_phys_alloc_range — allocate a memory block inside a specified range 🦋

🌸 SYNOPSIS 🌸

phys_addr_t memblock_phys_alloc_range (phys_addr_t size , phys_addr_t align , phys_addr_t start , phys_addr_t end );

like yes bestie it takes four args and returns a phys_addr_t, we love a consistent signature 👑

💖 ARGUMENTS 💖

  • size — how big the memory block you're allocating is, in bytes. this is the "how much snack do u want" number 🍓
  • align — the alignment of the region and of the block's size. yes both. it's a package deal, periodt ✨
  • start — the lower bound of the memory region you're allocating from, as a physical address 🫶
  • end — the upper bound of the memory region you're allocating from, as a physical address 🌈

🧚 DESCRIPTION 🧚

allocate size bytes in between start and end. that's it, that's the whole vibe check 💜 literally carve out size bytes somewhere in that window and you're slaying.

⭐ RETURN ⭐

the physical address of the allocated memory block on success 💅 — and 0 on failure 😭 (yes, zero is the "nope, didn't happen" signal, don't @ me).

🦋 SEE ALSO 🦋

the main character herself lives in the kernel file ./mm/memblock.c, and here's the whole group chat of related pages — every single one, no gatekeeping 👑:

💀 reminder bestie: this page is from ./mm and it's dated October 2026 — so if you're reading it, congrats, you're officially caught up. mwah, go allocate responsibly 😘💖

signed, your favorite kernel bestie 🎀✨ 🫶

📦 where this page comes from