Lines Matching full:memory

10 or more CPUs, local memory, and/or IO buses.  For brevity and to
24 Coherent NUMA or ccNUMA systems.   With ccNUMA systems, all memory is visible
28 Memory access time and effective memory bandwidth varies depending on how far
29 away the cell containing the CPU or IO bus making the memory access is from the
30 cell containing the target memory.  For example, access to memory by CPUs
32 bandwidths than accesses to memory on other, remote cells.  NUMA platforms
37 memory bandwidth.  However, to achieve scalable memory bandwidth, system and
38 application software must arrange for a large majority of the memory references
39 [cache misses] to be to "local" memory--memory on the same cell, if any--or
40 to the closest cell with memory.
48 CPUs, memory and/or IO buses.  And, again, memory accesses to memory on
54 physical cell that has no memory attached, and reassign any CPUs attached to
55 that cell to a node representing a cell that does have memory.  Thus, on
57 a given node will see the same local memory access times and bandwidth.
61 the existing nodes--or the system memory for non-NUMA platforms--into multiple
63 physical memory.  NUMA emluation is useful for testing NUMA kernel and
64 application features on non-NUMA platforms, and as a sort of memory resource
68 For each node with memory, Linux constructs an independent memory management
71 each memory zone [one or more of DMA, DMA32, NORMAL, HIGH_MEMORY, MOVABLE],
74 when a zone has no available memory to satisfy a request, is called
78 memory, Linux must decide whether to order the zonelists such that allocations
83 to the total memory of the node and the total memory of the system.  The
88 By default, Linux will attempt to satisfy memory allocation requests from the
96 Local allocation will tend to keep subsequent access to the allocated memory
98 as long as the task on whose behalf the kernel allocated some memory does not
99 later migrate away from that memory.  The Linux scheduler is aware of the
111 allocation behavior using Linux NUMA memory policy.
119 zones [nodes] with memory in the zonelists.  This means that for a memoryless
120 node the "local memory node"--the node of the first zone in CPU's node's
122 kernel selected as the nearest node with memory when it built the zonelists.
124 closest available memory.  This is a consequence of the same mechanism that
126 does contain memory overflows.
129 behavior.  Rather they want to be sure they get memory from the specified node
130 or get notified that the node has no free memory.  This is usually the case when
131 a subsystem allocates per CPU memory resources, for example.
135 numa_node_id() or CPU_to_node() functions and then request memory from only
137 may revert to its own fallback path.  The slab kernel memory allocator is an
145 memory exclusively from a node without memory.  To support such
147 or cpu_to_mem() function to locate the "local memory node" for the calling or