Lines Matching refs:flag
173 - cpuset.memory_migrate flag: if set, move pages to cpusets nodes
174 - cpuset.cpu_exclusive flag: is cpu placement exclusive?
175 - cpuset.mem_exclusive flag: is memory placement exclusive?
176 - cpuset.mem_hardwall flag: is memory allocation hardwalled
178 - cpuset.memory_spread_page flag: if set, spread page cache evenly on allowed nodes
179 - cpuset.memory_spread_slab flag: if set, spread slab cache evenly on allowed nodes
180 - cpuset.sched_load_balance flag: if set, load balance within CPUs on that cpuset
184 - cpuset.memory_pressure_enabled flag: compute memory_pressure?
272 that the cpuset_memory_pressure_enabled flag is zero. So only
305 There are two boolean flag files per cpuset that control where the
310 If the per-cpuset boolean flag file 'cpuset.memory_spread_page' is set, then
315 If the per-cpuset boolean flag file 'cpuset.memory_spread_slab' is set,
340 Both 'cpuset.memory_spread_page' and 'cpuset.memory_spread_slab' are boolean flag
347 Setting the flag 'cpuset.memory_spread_page' turns on a per-process flag
351 flag, and if set, a call to a new routine cpuset_mem_spread_node()
354 Similarly, setting 'cpuset.memory_spread_slab' turns on the flag
409 When the per-cpuset flag "cpuset.sched_load_balance" is enabled (the default
415 When the per-cpuset flag "cpuset.sched_load_balance" is disabled, then the
420 So, for example, if the top cpuset has the flag "cpuset.sched_load_balance"
422 CPUs, and the setting of the "cpuset.sched_load_balance" flag in any other
425 Therefore in the above two situations, the top cpuset flag
427 child cpusets have this flag enabled.
432 the particulars of this flag setting in descendant cpusets. Even if
448 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
454 between which cpusets have the flag "cpuset.sched_load_balance" enabled,
455 and the sched domain configuration. If a cpuset enables the flag, it
456 will get balancing across all its CPUs, but if it disables the flag,
458 cpuset enables the flag.
461 one of them has this flag enabled, then the other may find its
477 The per-cpuset flag 'cpuset.sched_load_balance' defaults to enabled (contrary
504 - the 'cpuset.sched_load_balance' flag of a cpuset with non-empty CPUs changes,
505 - or CPUs come or go from a cpuset with this flag enabled,
507 and with this flag enabled changes,
508 - or a cpuset with non-empty CPUs and with this flag enabled is removed,
568 belongs to. Therefore if the flag 'cpuset.sched_load_balance' of a cpuset
632 If the cpuset flag file 'cpuset.memory_migrate' is set true, then when
807 # /bin/echo 1 > cpuset.cpu_exclusive -> set flag 'cpuset.cpu_exclusive'
808 # /bin/echo 0 > cpuset.cpu_exclusive -> unset flag 'cpuset.cpu_exclusive'