memblock_all...xact_nid_raw(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 memblock_alloc_exact_nid_raw(9) 🌸

okay bestie, welcome to the Kernel API Manual 💖 this page is all about memblock_alloc_exact_nid_raw, and it's giving "allocate boot memory block on the exact node without zeroing memory" energy. no cap. ✨

🎀 NAME 🎀

memblock_alloc_exact_nid_raw — allocate boot memory block on the exact node without zeroing memory.

🦋 SYNOPSIS 🦋

void * memblock_alloc_exact_nid_raw (phys_addr_t size , phys_addr_t align , phys_addr_t min_addr , phys_addr_t max_addr , int nid );

💅 ARGUMENTS 💅

  • size — size of the memory block to be allocated, in bytes. 📏
  • align — alignment of the region and the block's size. 📐
  • min_addr — the lower bound of the memory region from where the allocation is preferred (a physical address). ⬇️
  • max_addr — the upper bound of the memory region from where the allocation is preferred (a physical address), or MEMBLOCK_ALLOC_ACCESSIBLE to allocate only from memory limited by the memblock.current_limit value. ⬆️
  • nid — the nid of the free area to find; NUMA_NO_NODE for any node. 🧚

🔥 DESCRIPTION 🔥

This is a public function — yes, public, bestie, it is not hiding — and it provides additional debug information (including caller info) if enabled. 👀

It does not zero allocated memory, periodt. So if you were expecting a fresh little zeroed-out block, that is not the vibe here. 💀

🌈 RETURN 🌈

Virtual address of the allocated memory block on success, NULL on failure. So: address = slay, NULL = nope. 😭

👑 SEE ALSO 👑

go read these next, iykyk:

okay bestie, that's the page 💖 source/version vibes: ./mm, October 2026. go allocate something cute (but not zeroed, remember 😭). 🫶💅

📦 where this page comes from