Lines Matching full:node

57 For some architectures, such as x86, Linux will "hide" any node representing a
59 that cell to a node representing a cell that does have memory.  Thus, on
61 a given node will see the same local memory access times and bandwidth.
66 nodes.  Each emulated node will manage a fraction of the underlying cells'
72 For each node with memory, Linux constructs an independent memory management
77 selected zone/node cannot satisfy the allocation request.  This situation,
83 fall back to the same zone type on a different node, or to a different zone
84 type on the same node.  This is an important consideration because some zones,
86 a default Node ordered zonelist. This means it tries to fallback to other zones
87 from the same node before using remote nodes which are ordered by NUMA distance.
90 node to which the CPU that executes the request is assigned.  Specifically,
91 Linux will attempt to allocate from the first node in the appropriate zonelist
92 for the node where the request originates.  This is called "local allocation."
93 If the "local" node cannot satisfy the request, the kernel will examine other
106 from their initial node and kernel data structures.
121 node the "local memory node"--the node of the first zone in CPU's node's
122 zonelist--will not be the node itself.  Rather, it will be the node that the
123 kernel selected as the nearest node with memory when it built the zonelists.
126 allows such allocations to fallback to other nearby nodes when a node that
130 behavior.  Rather they want to be sure they get memory from the specified node
131 or get notified that the node has no free memory.  This is usually the case when
134 A typical model for making such an allocation is to obtain the node id of the
135 node to which the "current CPU" is attached using one of the kernel's
137 the node id returned.  When such an allocation fails, the requesting subsystem
146 memory exclusively from a node without memory.  To support such
148 or cpu_to_mem() function to locate the "local memory node" for the calling or
149 specified CPU.  Again, this is the same node from which default, local page