Lines Matching refs:scheduler

57 CPUs or Memory Nodes not in that cpuset.  The scheduler will not
103 kernel to avoid any additional impact on the critical scheduler or
278     the system load imposed by a batch scheduler monitoring this
283     counter, a batch scheduler can detect memory pressure with a
288     the batch scheduler can obtain the key information, memory
376 The kernel scheduler (kernel/sched/core.c) automatically load balances
384 linearly with the number of CPUs being balanced.  So the scheduler
416 scheduler will avoid load balancing across the CPUs in that cpuset,
421 enabled, then the scheduler will have one sched domain covering all
434 scheduler might not consider the possibility of load balancing that
450 a task to a CPU outside its cpuset, but the scheduler load balancing
495 The internal kernel cpuset to scheduler interface passes from the
496 cpuset code to the scheduler code a partition of the load balanced
502 scheduler sched domain setup code, to have the sched domains rebuilt
511 This partition exactly defines what sched domains the scheduler should
515 The scheduler remembers the currently active sched domain partitions.
516 When the scheduler routine partition_sched_domains() is invoked from
525 In sched domain, the scheduler migrates tasks in 2 ways; periodic load
528 When a task is woken up, scheduler try to move the task on idle CPU.
531 then scheduler migrate task B to CPU Y so that task B can start on
539 idle CPUs, the scheduler might not search all CPUs in the domain
545 is idle while CPU X and the siblings are busy, scheduler can't migrate
594 code, such as the scheduler, and due to the fact that the kernel