Lines Matching refs:per

248 The memory_pressure of a cpuset provides a simple per-cpuset metric
275 Why a per-cpuset, running average:
277     Because this meter is per-cpuset, rather than per-task or mm,
287     Because this meter is per-cpuset rather than per-task or mm,
293 A per-cpuset simple digital filter (requires a spinlock and 3 words
294 of data per-cpuset) is kept, and updated by any task attached to that
297 A per-cpuset file provides an integer number representing the recent
299 the tasks in the cpuset, in units of reclaims attempted per second,
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,
347 Setting the flag 'cpuset.memory_spread_page' turns on a per-process flag
359 value of a per-task rotor cpuset_mem_spread_rotor to select the next
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
477 The per-cpuset flag 'cpuset.sched_load_balance' defaults to enabled (contrary
567 This file is per-cpuset and affect the sched domain where the cpuset
603 in the task's cpuset, and update its per-task memory placement to
833 A: We can only return one error code per call to write(). So you should also