Lines Matching refs:then

310 If the per-cpuset boolean flag file 'cpuset.memory_spread_page' is set, then
316 then the kernel will spread some file system related slab caches,
337 is turned off, then the currently specified NUMA mempolicy once again
342 for that cpuset.  If a "1" is written to that file, then that turns
415 When the per-cpuset flag "cpuset.sched_load_balance" is disabled, then the
421 enabled, then the scheduler will have one sched domain covering all
448 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
461 one of them has this flag enabled, then the other may find its
484 then they will be (must be) both in the same sched domain.
487 then by the above that means there is a single sched domain covering
531 then scheduler migrate task B to CPU Y so that task B can start on
569 is disabled, then 'cpuset.sched_relax_domain_level' have no effect since
574 requests 0 and others are -1 then 0 is used.
587 then increasing 'sched_relax_domain_level' would benefit you.
600 If a cpuset has its Memory Nodes modified, then for each task attached
606 its new cpuset, then the task will continue to use whatever subset
609 in the new cpuset, then the task will be essentially treated as if it
612 from one cpuset to another, then the kernel will adjust the task's
616 If a cpuset has its 'cpuset.cpus' modified, then each task in that cpuset
618 if a task's pid is written to another cpusets 'cpuset.tasks' file, then its
629 of main memory) then that page stays on whatever node it
632 If the cpuset flag file 'cpuset.memory_migrate' is set true, then when
638 then the page will be placed on the second valid node of the new cpuset.
640 Also if 'cpuset.memory_migrate' is set true, then if that cpuset's
649 then all the tasks in that cpuset will be moved to the nearest ancestor
664 the current task's cpuset, then we relax the cpuset, and look for
681 and then start a subshell 'sh' in that cpuset: