try_offline_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… try_offline_node β€” Kernel API Manual ✨

okay so bestie, welcome to the try_offline_node(9) page 🫢 it's a lil kernel API moment, and honestly? she's short but she matters. let's get into it πŸ’–


🌸 NAME 🌸

try_offline_node β€” (and yes the original literally leaves the description blank, no cap, not me making that up 😭 she's mysterious like that)


✨ SYNOPSIS ✨

void try_offline_node (int nid );

that's it. that's the whole signature. clean, simple, iconic πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • nid β€” the node ID πŸ’« literally just which node we're talking about, that's the whole vibe check

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she do? okay so listen: try_offline_node offlines a node β€” but only if all memory sections and cpus of the node are removed. both conditions, bestie. memory sections βœ”οΈ cpus βœ”οΈ then she'll offline that node for you. it's giving conditional queen energy πŸ‘‘ if stuff's still hanging around on that node, she's simply not doing it, periodt πŸ’…


⚠️ NOTE ⚠️

🚨 real talk, don't skip this one 🚨 the caller must call lock_device_hotplug to serialize hotplug and online/offline operations before this call. like, before-before. this is not a suggestion, it's the rule πŸ™ˆ skipping the lock is how you get chaotic race condition energy and nobody wants that 😭

⭐ SEE ALSO ⭐

kernel file ./mm/memory_hotplug.c πŸ—‚οΈ and her besties:

go read them, iykyk πŸ’œ


and that's the page!! πŸŽ€ written from the ./mm corner of the kernel, dated October 2026 ⭐ thanks for reading bestie, go call lock_device_hotplug first fr fr πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from