|
@@ -445,7 +445,7 @@ across partially overlapping sets of CPUs would risk unstable dynamics
|
|
|
that would be beyond our understanding. So if each of two partially
|
|
|
overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
|
|
|
form a single sched domain that is a superset of both. We won't move
|
|
|
-a task to a CPU outside it cpuset, but the scheduler load balancing
|
|
|
+a task to a CPU outside its cpuset, but the scheduler load balancing
|
|
|
code might waste some compute cycles considering that possibility.
|
|
|
|
|
|
This mismatch is why there is not a simple one-to-one relation
|
|
@@ -552,8 +552,8 @@ otherwise initial value -1 that indicates the cpuset has no request.
|
|
|
1 : search siblings (hyperthreads in a core).
|
|
|
2 : search cores in a package.
|
|
|
3 : search cpus in a node [= system wide on non-NUMA system]
|
|
|
- ( 4 : search nodes in a chunk of node [on NUMA system] )
|
|
|
- ( 5 : search system wide [on NUMA system] )
|
|
|
+ 4 : search nodes in a chunk of node [on NUMA system]
|
|
|
+ 5 : search system wide [on NUMA system]
|
|
|
|
|
|
The system default is architecture dependent. The system default
|
|
|
can be changed using the relax_domain_level= boot parameter.
|