Lines Matching full:domain

5 Each CPU has a "base" scheduling domain (struct sched_domain). The domain
7 MUST be NULL terminated, and domain structures should be per-CPU as they are
10 Each scheduling domain spans a number of CPUs (stored in the ->span field).
11 A domain's span MUST be a superset of it child's span (this restriction could
12 be relaxed if the need arises), and a base domain for CPU i MUST span at least
13 i. The top domain for each CPU will generally span all CPUs in the system
16 explicitly set. A sched domain's span means "balance process load among these
19 Each scheduling domain must have one or more CPU groups (struct sched_group)
22 domain's span. The group pointed to by the ->groups pointer MUST contain the CPU
23 to which the domain belongs. Groups may be shared among CPUs as they contain
26 flag is set on the corresponding scheduling domain and its groups may not be
29 Balancing within a sched domain occurs between groups. That is, each group
42 our CPU is on, starting from its base domain and going up the ->parent chain.
43 While doing that, it checks to see if the current domain has exhausted its
44 rebalance interval. If so, it runs load_balance() on that domain. It then checks
48 Initially, load_balance() finds the busiest group in the current sched domain.
53 computed while iterating over this sched domain's groups.
58 The "base" domain will "span" the first level of the hierarchy. In the case
62 In SMP, the parent of the base domain will span all physical CPUs in the
64 of the SMP domain will span the entire machine, with each group having the
66 might have just one domain covering its one NUMA level.
73 while using the generic domain builder in kernel/sched/core.c if they wish to
77 Alternatively, the architecture may completely override the generic domain
85 the domain structure in a visual format.