__remove_memory(9)
π NAME π
Okay bestie, meet __remove_memory(9) from the Kernel API Manual β its whole mission is: remove memory if every memory block is offline. That's the vibe. No cap. π
β¨ SYNOPSIS β¨
void __remove_memory (u64 start , u64 size );
π«Ά ARGUMENTS π«Ά
startβ physical address of the region to remove. Like, where the memory situation starts. πsizeβ size of the region to remove. The amount of memory we're talking about, bestie. π
β οΈ NOTE β οΈ
Before this call, the caller must call lock_device_hotplug so that hotplug and online/offline operations are serialized. This is required by try_offline_node, so don't skip it β it's giving "mandatory pre-game ritual." π¨
Real talk: that serialization requirement is not decorative; it's literally required by try_offline_node.
π SEE ALSO π
Kernel file ./mm/memory_hotplug.c, plus these besties:
__remove_pages(9)__add_memory_driver_managed(9)add_memory_driver_managed(9)try_offline_node(9)offline_and_remove_memory_ranges(9)
From ./mm, the October 2026 version/date drop, page __remove_memory(9) β bye bestie, hydrate and serialize your hotplug ops! πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms