Lines Matching refs:Memory

40 Cpusets provide a mechanism for assigning a set of CPUs and Memory
41 Nodes to a set of tasks.   In this document "Memory Node" refers to
44 Cpusets constrain the CPU and Memory placement of tasks to only
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
57 CPUs or Memory Nodes not in that cpuset.  The scheduler will not
64 cpusets and which CPUs and Memory Nodes are assigned to each cpuset,
73 complex memory cache hierarchies and multiple Memory Nodes having
79 the available CPU and Memory resources amongst the requesting tasks.
102 leverages existing CPU and Memory Placement facilities in the Linux
111 Memory Nodes are used by a process or set of processes.
114 CPUs a task may be scheduled (sched_setaffinity) and on which Memory
119  - Cpusets are sets of allowed CPUs and Memory Nodes, known to the
126    those Memory Nodes allowed in that task's cpuset.
127  - The root cpuset contains all the systems CPUs and Memory
130    of the parents CPU and Memory Node resources.
135    any overlapping CPUs or Memory Nodes.
148    Memory Nodes by what's allowed in that task's cpuset.
159 and mems_allowed (on which Memory Nodes it may obtain memory),
172  - cpuset.mems: list of Memory Nodes in that cpuset
188 CPUs and Memory Nodes, and attached tasks, are modified by writing
197 to using the CPUs and Memory Nodes of a particular cpuset.  A task
207  - Its CPUs and Memory Nodes must be a subset of its parents.
230 Memory Nodes.
591 or Memory Node placement, or of changing to which cpuset a task
594 If a cpuset has its Memory Nodes modified, then for each task attached
649 functionality for removing Memory Nodes is available, a similar exception
652 its allowed CPUs or Memory Nodes taken offline.
674 named "Charlie", containing just CPUs 2 and 3, and Memory Node 1,
738 the CPUs and Memory Nodes it can use, the processes that are using