admin-guide/cgroup-v1/cpusets.rst

176  - cpuset.memory_migrate flag: if set, move pages to cpusets nodes
177  - cpuset.cpu_exclusive flag: is cpu placement exclusive?
178  - cpuset.mem_exclusive flag: is memory placement exclusive?
179  - cpuset.mem_hardwall flag:  is memory allocation hardwalled
181  - cpuset.memory_spread_page flag: if set, spread page cache evenly on allowed nodes
182  - cpuset.memory_spread_slab flag: if set, spread slab cache evenly on allowed nodes
183  - cpuset.sched_load_balance flag: if set, load balance within CPUs on that cpuset
188  - cpuset.memory_pressure_enabled flag: compute memory_pressure?
288     that the cpuset_memory_pressure_enabled flag is zero.  So only
321 There are two boolean flag files per cpuset that control where the
326 If the per-cpuset boolean flag file 'cpuset.memory_spread_page' is set, then
331 If the per-cpuset boolean flag file 'cpuset.memory_spread_slab' is set,
356 Both 'cpuset.memory_spread_page' and 'cpuset.memory_spread_slab' are boolean flag
363 Setting the flag 'cpuset.memory_spread_page' turns on a per-process flag
367 flag, and if set, a call to a new routine cpuset_mem_spread_node()
370 Similarly, setting 'cpuset.memory_spread_slab' turns on the flag
426 When the per-cpuset flag "cpuset.sched_load_balance" is enabled (the default
432 When the per-cpuset flag "cpuset.sched_load_balance" is disabled, then the
437 So, for example, if the top cpuset has the flag "cpuset.sched_load_balance"
439 CPUs, and the setting of the "cpuset.sched_load_balance" flag in any other
442 Therefore in the above two situations, the top cpuset flag
444 child cpusets have this flag enabled.
449 the particulars of this flag setting in descendant cpusets.  Even if
465 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
471 between which cpusets have the flag "cpuset.sched_load_balance" enabled,
472 and the sched domain configuration.  If a cpuset enables the flag, it
473 will get balancing across all its CPUs, but if it disables the flag,
475 cpuset enables the flag.
478 one of them has this flag enabled, then the other may find its
494 The per-cpuset flag 'cpuset.sched_load_balance' defaults to enabled (contrary
522  - the 'cpuset.sched_load_balance' flag of a cpuset with non-empty CPUs changes,
523  - or CPUs come or go from a cpuset with this flag enabled,
525    and with this flag enabled changes,
526  - or a cpuset with non-empty CPUs and with this flag enabled is removed,
588 belongs to.  Therefore if the flag 'cpuset.sched_load_balance' of a cpuset
653 If the cpuset flag file 'cpuset.memory_migrate' is set true, then when
839   # /bin/echo 1 > cpuset.cpu_exclusive 	-> set flag 'cpuset.cpu_exclusive'
840   # /bin/echo 0 > cpuset.cpu_exclusive 	-> unset flag 'cpuset.cpu_exclusive'