numa_add_reserved_memblk(9)

📦 version 7.3.1, in nixpkgs unstable

💅 numa_add_reserved_memblk(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's a kernel function called numa_add_reserved_memblk, and honestly? it's giving "small function, big job." let's get into it 🫶

✨ NAME ✨

numa_add_reserved_memblk — literally just adds one numa_memblk to numa_reserved_meminfo. that's the whole vibe. no cap. 🎀

🌸 SYNOPSIS 🌸

int numa_add_reserved_memblk (int nid , u64 start , u64 end );

🦋 ARGUMENTS 🦋

  • nid — the NUMA node ID of the new memblk. which node this lil guy belongs to, basically 💫
  • start — the start address of the new memblk. where it begins, fr fr 📍
  • end — the end address</end> of the new memblk. where it wraps up 🎯

💖 DESCRIPTION 💖

so what it does: it adds a brand-new memblk to the numa_reserved_meminfo. slay. that's it. ✨

Usage Case: okay this is the fun part. numa_cleanup_meminfo reconciles all the numa_memblk instances against memblock_type information, and it moves any that intersect reserved ranges over to numa_reserved_meminfo. very "sorting your laundry into piles" energy 🧺

but — and here's the plot twist — when that information is known ahead of time, we use numa_add_reserved_memblk to add the numa_memblk to numa_reserved_meminfo directly. no middleman, no cleanup pass, just straight in. main character energy honestly 👑

🔥 RETURN 🔥

  • 0 on success 💚
  • -errno on failure 😭 (yeah, it hands you back a negative errno, classic)

👑 SEE ALSO 👑

Kernel file ./mm/numa_memblks.c, plus the whole friend group:

ngl, that's a whole squad and they all live in ./mm/numa_memblks.c — go say hi 🫶

and that's the page, bestie! sign-off time: this iconic little doc comes from the source tree at ./mm, dated October 2026. take care of her 💜🌸✨

📦 where this page comes from