Lines Matching refs:domain

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
6 Each scheduling domain spans a number of CPUs (stored in the ->span field).
7 A domain's span MUST be a superset of it child's span (this restriction could
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
12 explicitly set. A sched domain's span means "balance process load among these
15 Each scheduling domain must have one or more CPU groups (struct sched_group)
18 domain's span. The intersection of cpumasks from any two of these groups
20 contain the CPU to which the domain belongs. Groups may be shared among
23 Balancing within a sched domain occurs between groups. That is, each group
36 our CPU is on, starting from its base domain and going up the ->parent chain.
37 While doing that, it checks to see if the current domain has exhausted its
38 rebalance interval. If so, it runs load_balance() on that domain. It then checks
42 Initially, load_balance() finds the busiest group in the current sched domain.
47 computed while iterating over this sched domain's groups.
50 The "base" domain will "span" the first level of the hierarchy. In the case
54 In SMP, the parent of the base domain will span all physical CPUs in the
56 of the SMP domain will span the entire machine, with each group having the
58 might have just one domain covering its one NUMA level.
65 while using the generic domain builder in kernel/sched/core.c if they wish to
69 Alternatively, the architecture may completely override the generic domain
77 the domain structure in a visual format.