memory_block_add_nid_early(9)

okay so bestie, welcome to the Kernel API Manual — today’s main character is literally memory_block_add_nid_early(9) and she has lore 💅✨

🌸 NAME 🌸

memory_block_add_nid_early — Indicate that early system RAM falling into this memory block device (partially) belongs to the given node. periodt.

✨ SYNOPSIS ✨

void memory_block_add_nid_early (struct memory_block *mem , int nid );

🫶 ARGUMENTS 🫶

• mem — The memory block device. that’s the vibe.
• nid — The node id. yep, that one.

💖 DESCRIPTION 💖

Okay so picture this: you gotta indicate that early system RAM falling into this memory block (partially) belongs to the given node. that’s the whole assignment, no cap 🎀

And not only that — this will also properly set/adjust mem->zone based on the zone ranges of the given node. iconic behavior, ngl ✨

Memory hotplug handles this on memory block creation, where we can only have a single nid span a memory block. that’s the rule, fr fr 💀

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/memory.c — go read it, iykyk — plus these besties:

• memory_block_advise_max_size(9)
• memory_block_advised_max_size(9)
• walk_memory_blocks(9)
• for_each_memory_block(9)
• memory_group_register_static(9)
• memory_group_register_dynamic(9)
• memory_group_unregister(9)

mwah 💋 this lil page comes from ./drivers/base, is dated October 2026, and it’s literally memory_block_add_nid_early(9) — slay and goodbye 🦋💜