Lines Matching full:scheduler

60 CPUs or Memory Nodes not in that cpuset.  The scheduler will not
106 kernel to avoid any additional impact on the critical scheduler or
294     the system load imposed by a batch scheduler monitoring this
299     counter, a batch scheduler can detect memory pressure with a
304     the batch scheduler can obtain the key information, memory
392 The kernel scheduler (kernel/sched/core.c) automatically load balances
400 linearly with the number of CPUs being balanced.  So the scheduler
433 scheduler will avoid load balancing across the CPUs in that cpuset,
438 enabled, then the scheduler will have one sched domain covering all
451 scheduler might not consider the possibility of load balancing that
467 a task to a CPU outside its cpuset, but the scheduler load balancing
512 The internal kernel cpuset to scheduler interface passes from the
513 cpuset code to the scheduler code a partition of the load balanced
519 scheduler sched domain setup code, to have the sched domains rebuilt
529 This partition exactly defines what sched domains the scheduler should
533 The scheduler remembers the currently active sched domain partitions.
534 When the scheduler routine partition_sched_domains() is invoked from
543 In sched domain, the scheduler migrates tasks in 2 ways; periodic load
546 When a task is woken up, scheduler try to move the task on idle CPU.
549 then scheduler migrate task B to CPU Y so that task B can start on
557 idle CPUs, the scheduler might not search all CPUs in the domain
563 is idle while CPU X and the siblings are busy, scheduler can't migrate
615 code, such as the scheduler, and due to the fact that the kernel