Lines Matching refs:CPU

44 Cpusets constrain the CPU and Memory placement of tasks to only
54 include CPUs in its CPU affinity mask, and using the mbind(2) and
58 schedule a task on a CPU that is not allowed in its cpus_allowed
79 the available CPU and Memory resources amongst the requesting tasks.
102 leverages existing CPU and Memory Placement facilities in the Linux
130    of the parents CPU and Memory Node resources.
220 cpu_online_mask using a CPU hotplug notifier, and the mems file
377 tasks.  If one CPU is underutilized, kernel code running on that
378 CPU will look for tasks on other more overloaded CPUs and move those
413 from any CPU in that cpuset to any other.
430 the top cpuset that might use non-trivial amounts of CPU, as such tasks
433 such a task could use spare CPU cycles in some other CPUs, the kernel
435 task to that underused CPU.
437 Of course, tasks pinned to a particular CPU can be left in a cpuset
443 overlap and each CPU is in at most one sched domain.
450 a task to a CPU outside its cpuset, but the scheduler load balancing
465 don't leave tasks that might use non-trivial amounts of CPU in
528 When a task is woken up, scheduler try to move the task on idle CPU.
529 For example, if a task A running on CPU X activates another task B
530 on the same CPU X, and if CPU Y is X's sibling and performing idle,
531 then scheduler migrate task B to CPU Y so that task B can start on
532 CPU Y without waiting task A on CPU X.
534 And if a CPU run out of tasks in its runqueue, the CPU try to pull
541 events are limited in the same socket or node where the CPU locates,
544 For example, assume CPU Z is relatively far from CPU X.  Even if CPU Z
545 is idle while CPU X and the siblings are busy, scheduler can't migrate
547 As the result, task B on CPU X need to wait task A or wait load balance
583    special hardware support for CPU cache etc.
596 task directly, the impact on a task of changing its cpuset CPU
617 will have its allowed CPU placement changed immediately.  Similarly,
619 allowed CPU placement is changed immediately.  If such a task had been
621 the task will be allowed to run on any CPU allowed in its new cpuset,
790 To add a CPU to a cpuset, write the new list of CPUs including the
791 CPU to be added. To add 6 to the above cpuset:
795 Similarly to remove a CPU from a cpuset, write the new list of CPUs
796 without the CPU to be removed.