Lines Matching refs:sched

145  - in sched.c migrate_live_tasks(), to keep migrating tasks within
376 The kernel scheduler (kernel/sched/core.c) automatically load balances
385 has support to partition the systems CPUs into a number of sched
386 domains such that it only load balances within each sched domain.
387 Each sched domain covers some subset of the CPUs in the system;
388 no two sched domains overlap; some CPUs might not be in any sched
391 Put simply, it costs less to balance between two smaller sched domains
395 By default, there is one sched domain covering all CPUs, including those
411 be contained in a single sched domain, ensuring that load balancing
421 enabled, then the scheduler will have one sched domain covering all
441 There is an impedance mismatch here, between cpusets and sched domains.
443 overlap and each CPU is in at most one sched domain.
445 It is necessary for sched domains to be flat because load balancing
449 form a single sched domain that is a superset of both.  We won't move
455 and the sched domain configuration.  If a cpuset enables the flag, it
481 in the same sched domain.)
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
491 where it can.  It will pick as fine a granularity partition of sched
502 scheduler sched domain setup code, to have the sched domains rebuilt
511 This partition exactly defines what sched domains the scheduler should
512 setup - one sched domain for each element (struct cpumask) in the
515 The scheduler remembers the currently active sched domain partitions.
517 the cpuset code to update these sched domains, it compares the new
518 partition requested with the current, and updates its sched domains,
525 In sched domain, the scheduler migrates tasks in 2 ways; periodic load
567 This file is per-cpuset and affect the sched domain where the cpuset
570 there is no sched domain belonging the cpuset.
572 If multiple cpusets are overlapping and hence they form a single sched