Lines Matching refs:CPU

1 Each CPU has a "base" scheduling domain (struct sched_domain). The domain
3 MUST be NULL terminated, and domain structures should be per-CPU as they are
8 be relaxed if the need arises), and a base domain for CPU i MUST span at least
9 i. The top domain for each CPU will generally span all CPUs in the system
15 Each scheduling domain must have one or more CPU groups (struct sched_group)
20 contain the CPU to which the domain belongs. Groups may be shared among
28 In kernel/sched/core.c, trigger_load_balance() is run periodically on each CPU
34 The latter function takes two arguments: the current CPU and whether it was idle
36 our CPU is on, starting from its base domain and going up the ->parent chain.
45 CPU's runqueue and the newly found busiest one and starts moving tasks from it
51 of SMT, you'll span all siblings of the physical CPU, with each group being
52 a single virtual CPU.
55 node. Each group being a single physical CPU. Then with NUMA, the parent