Lines Matching full:mems
99 * cpuset.cpus and cpuset.mems, and won't be limited by the
442 * Cgroup v2 behavior is used on the "cpus" and "mems" control files when
445 * With v2 behavior, "cpus" and "mems" are always what the users have
447 * cpus or mems will be affected.
536 * online mems. The top cpuset always has some mems online.
2111 * parent, which is guaranteed to have some MEMs. in update_nodemasks_hier()
2142 * Handle user request to change the 'mems' memory placement
2674 * in effective cpus and mems. In that case, we can optimize out in cpuset_attach()
2833 * Common handling for a write to a "cpus" or "mems" file.
2850 * As writes to "cpus" or "mems" may restore @cs's execution in cpuset_write_resmask()
3066 .name = "mems",
3173 .name = "mems",
3188 .name = "mems.effective",
3304 * (and likewise for mems) to the new cgroup. in cpuset_css_online()
3784 /* fetch the available cpus/mems and find out which changed how */ in cpuset_hotplug_workfn()
3841 /* if cpus or mems changed, we need to propagate to descendants */ in cpuset_hotplug_workfn()
4101 * GFP_USER - only nodes in current tasks mems allowed ok.