Lines Matching refs:memory

22   1.6 What is memory spread ?
42 an on-line node that contains memory.
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
73 complex memory cache hierarchies and multiple Memory Nodes having
75 the efficient scheduling and memory placement of processes.
82 memory placement to reduce memory access times and contention,
98 when the memory locations are changed.
104 memory allocator code.
115 Nodes it may obtain memory (mbind, set_mempolicy).
149  - in page_alloc.c, to restrict memory to allowed nodes.
159 and mems_allowed (on which Memory Nodes it may obtain memory),
175  - cpuset.mem_exclusive flag: is memory placement exclusive?
176  - cpuset.mem_hardwall flag:  is memory allocation hardwalled
202 the detailed placement done on individual tasks and memory regions
209  - If its cpu or memory is exclusive, they may not overlap any sibling.
222 nodes with memory--using the cpuset_track_online_nodes() hook.
235 whether hardwalled or not, restrict allocations of memory for user
241 Only a small amount of typical kernel memory, such as requests from
250 use memory on the nodes of the cpuset to satisfy additional memory
254 cpusets to efficiently detect what level of memory pressure that job
259 are trying to use more memory than allowed on the nodes assigned to them,
262 goals if they start to use more memory than allowed to them.
265 to monitor a cpuset for signs of memory pressure.  It's up to the
283     counter, a batch scheduler can detect memory pressure with a
288     the batch scheduler can obtain the key information, memory
303 1.6 What is memory spread ?
324 By default, both kinds of memory spreading are off, and memory
327 configuration, so long as sufficient free memory pages are available.
329 When new cpusets are created, they inherit the memory spread settings
332 Setting memory spreading causes allocations for the affected page
336 their containing task's memory spread settings.  If memory spreading
338 applies to memory page allocations.
362 This memory placement policy is also known (in other contexts) as
370 data set, the memory allocation across the nodes in the jobs cpuset
595 does not support one task updating the memory placement of another
602 a page of memory for that task, the kernel will notice the change
603 in the task's cpuset, and update its per-task memory placement to
604 remain within the new cpusets memory placement.  If the task was using
613 memory placement, as above, the next time that the kernel attempts
614 to allocate a page of memory for that task.
624 In summary, the memory placement of a task whose cpuset is changed is
629 of main memory) then that page stays on whatever node it
631 cpusets memory placement policy 'cpuset.mems' subsequently changes.
654 their cpus_allowed to allow all online CPUs.  When memory hotplug
665 memory anywhere we can find it.  It's better to violate the cpuset