cpuset_prin...mems_allowed(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cpuset_prin...mems_allowed(9) ✨

okay so this is from the Kernel API Manual (yes, the kernel API manual, we're literally in the kernel bestie, put your hard hat on πŸ‘“) and it's about cpuset_print_current_mems_allowed. it's giving "one tiny function that just wants to gossip about the current task." no cap.


🌸 NAME 🌸

cpuset_print_current_mems_allowed β€” prints current's cpuset and mems_allowed πŸ’…

like. that's it. that's the whole job. it prints stuff about current.


πŸŽ€ SYNOPSIS πŸŽ€

void cpuset_print_current_mems_allowed (void );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” no arguments. zero. none. she takes nothing, she needs nothing, she is self-sufficient, main character energy fr fr ✨

πŸ’– DESCRIPTION πŸ’–

so what she does is she prints current's name, the cpuset name, and a cached copy of its mems_allowed β€” and where does all that go? straight to the kernel log. πŸ“

that's the whole vibe check. name, cpuset name, cached mems_allowed, kernel log. iconic, lowkey, done. 🫢


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./kernel/cgroup/cpuset.c β€” and honestly the whole cpuset friend group showed up to the group chat, come say hi:


bestie please note: the page header up top also carries our source/location ./kernel/cgroup and the date October 2026, so this whole thing is catalogued as cpuset_prin...mems_allowed(9) out of ./kernel/cgroup, dated October 2026. mwah πŸ’‹ periodt.

that's the page!! go read a cpuset, ily, bye πŸ§šβ€β™€οΈπŸ’œ

πŸ“¦ where this page comes from