Lines Matching full:mems
287 * Cgroup v2 behavior is used on the "cpus" and "mems" control files when
290 * With v2 behavior, "cpus" and "mems" are always what the users have
292 * cpus or mems will be affected.
369 * online mems. The top cpuset always has some mems online.
2592 * parent, which is guaranteed to have some MEMs. in update_nodemasks_hier()
2623 * Handle user request to change the 'mems' memory placement
3034 * in effective cpus and mems. In that case, we can optimize out in cpuset_attach()
3095 * Common handling for a write to a "cpus" or "mems" file.
3112 * As writes to "cpus" or "mems" may restore @cs's execution in cpuset_write_resmask()
3291 .name = "mems",
3306 .name = "mems.effective",
3440 * (and likewise for mems) to the new cgroup. in cpuset_css_online()
3829 /* fetch the available cpus/mems and find out which changed how */ in cpuset_handle_hotplug()
3880 /* if cpus or mems changed, we need to propagate to descendants */ in cpuset_handle_hotplug()
4135 * GFP_USER - only nodes in current tasks mems allowed ok.