offline_and_...emory_ranges(9)

💖 NAME 💖

okay so bestie, this is the Kernel API Manual page for offline_and_...emory_ranges(9) — and the function is literally offline_and_remove_memory_ranges — offline and remove multiple memory ranges ✨.

✨ SYNOPSIS ✨

int offline_and_remove_memory_ranges (const struct range *ranges , unsigned int nr_ranges );

🎀 ARGUMENTS 🎀

• ranges — array of physical address ranges to offline and remove 🫶
• nr_ranges — number of entries in ranges 💅

🦋 DESCRIPTION 🦋

okay so this is the group project that actually works: she offlines and removes several memory ranges as one operation, serialized against other hotplug operations by a single lock_device_hotplug 🔥.

The order is the whole vibe: this offlines all ranges before removing any of them. If offlining any range fails, the entire process is reverted and nothing is removed 😭. That gives you a fully atomic semantic for unplugging an entire device — no half-unplugged chaos, periodt.

Each range must be memory-block aligned in start and size — that is not optional, bestie 🎀.

🌸 RETURN 🌸

• 0 on success 🎉
• negative errno on failure (never positive) 💀

On failure, no range has been removed. Highkey iconic safety behavior, honestly.

🔥 SEE ALSO 🔥

• Kernel file ./mm/memory_hotplug.c: __remove_pages(9), __add_memory_driver_managed(9), add_memory_driver_managed(9), try_offline_node(9), __remove_memory(9) 👑

kisses bestie, that’s the whole page 💋 — source/version ./mm, date October 2026, and the manual page is offline_and_...emory_ranges(9) 🫶✨