memory_block...ise_max_size(9)

💖 memory_block_advise_max_size(9) 💖

okay so welcome to the Kernel API Manual, bestie — this page is all about memory_block_advise_max_size, and it’s giving “tiny function, very specific job.” let’s get into it 🎀

---

🌸 NAME 🌸

memory_block_advise_max_size — advise memory hotplug on the max suggested block size, usually for alignment. that’s the whole vibe ✨

✨ SYNOPSIS ✨

the call looks like this, fr fr:

int memory_block_advise_max_size (unsigned long size );

🦋 ARGUMENTS 🦋

• size — the suggestion for the maximum block size. bestie, it must be aligned on power of 2. no exceptions, periodt 💅

🎀 DESCRIPTION 🎀

Early boot software (pre-allocator init) may advise archs on the max block size. lowkey important early-boot business 🧚

This value can only decrease after initialization, because the intent is to identify the largest supported alignment for all sources. so like… it can go down, not up, and that’s on purpose 💖

Use of this value is arch-defined, as is min/max block size. iykyk — the arch gets to decide how this all works 🌈

🔥 RETURN 🔥

• 0 — on success. slay ✅
• -EINVAL — if size is 0 or not pow2 aligned. bestie, check your alignment 😭
• -EBUSY — if the value has already been probed. it’s already been through enough, okay? 💀

👑 SEE ALSO 👑

• Kernel file ./drivers/base/memory.c
• memory_block_advised_max_size(9)
• memory_block_add_nid_early(9)
• walk_memory_blocks(9)
• for_each_memory_block(9)
• memory_group_register_static(9)
• memory_group_register_dynamic(9)
• memory_group_unregister(9)

---

okay that’s the page, bestie 💅 stay aligned and hydrated 🫶 kisses from source ./drivers/base, dated October 2026, page title memory_block...ise_max_size(9) 🎀✨💖