Lines Matching refs:t
212 - It can't be marked exclusive unless its parent is.
405 domain and hence won't be load balanced.
409 two domains won't be load balanced to the other one.
440 cpusets won't matter, as we're already fully load balancing.
446 When doing this, you don't usually want to leave any unpinned tasks in
455 that disables "cpuset.sched_load_balance" as those tasks aren't going anywhere
459 Cpusets are hierarchical and nest. Sched domains are flat; they don't
466 form a single sched domain that is a superset of both. We won't move
482 don't leave tasks that might use non-trivial amounts of CPU in
563 is idle while CPU X and the siblings are busy, scheduler can't migrate
598 Don't modify this file if you are not sure.
605 - The searching cost doesn't have impact(for you) or you can make
632 as queried by get_mempolicy(), doesn't change). If a task is moved
692 2) mount -t cgroup -ocpuset cpuset /sys/fs/cgroup/cpuset
704 mount -t cgroup -ocpuset cpuset /sys/fs/cgroup/cpuset
741 # mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset
806 mount -t cpuset X /sys/fs/cgroup/cpuset
810 mount -t cgroup -ocpuset,noprefix X /sys/fs/cgroup/cpuset
866 errors. If you use it in the cpuset file system, you won't be