Lines Matching refs:node
20 Each bank is called a node and the concept is represented under Linux by a
23 for a particular node can be referenced by ``NODE_DATA(nid)`` macro where
24 ``nid`` is the ID of that node.
26 For NUMA architectures, the node structures are allocated by the architecture
35 The memory range within a node that corresponds to a particular zone is
81 The relation between node and zone extents is determined by the physical memory
86 entire memory will be on node 0 and there will be three zones: ``ZONE_DMA``,
91 | node 0 |
103 ``ZONE_NORMAL`` and ``ZONE_MOVABLE`` on node 0, and ``ZONE_NORMAL`` and
104 ``ZONE_MOVABLE`` on node 1::
109 | node 0 | | node 1 |
119 machine has 16 Gbytes of RAM in 4 memory banks, even banks belong to node 0
120 and odd banks belong to node 1::
125 | node 0 | | node 1 | | node 0 | | node 1 |
133 In this case node 0 will span from 0 to 12 Gbytes and node 1 will span from
141 As we have mentioned, each node in memory is described by a ``pg_data_t`` which
143 Linux uses a node-local allocation policy to allocate memory from the node
145 likely the memory from the current node will be used. The allocation policy can
149 Most NUMA architectures maintain an array of pointers to the node
152 firmware. The bulk of the node initialization happens slightly later in the
157 Along with the node structures, kernel maintains an array of ``nodemask_t``
162 The node could become online at some point.
164 The node is online.
166 The node has regular memory.
168 The node has regular or high memory. When ``CONFIG_HIGHMEM`` is disabled
171 The node has memory(regular, high, movable)
173 The node has one or more CPUs
175 For each node that has a property described above, the bit corresponding to the
176 node ID in the ``node_states[<property>]`` bitmask is set.
178 For example, for node 2 with normal memory and CPUs, bit 2 will be set in ::
190 Among other things, nodemasks are used to provide macros for node traversal,
193 For instance, to call a function foo() for each online node::
212 The zones for this node. Not all of the zones may be populated, but it is
213 the full list. It is referenced by this node's node_zonelists as well as
214 other node's node_zonelists.
223 Number of populated zones in this node.
226 For UMA systems that use FLATMEM memory model the 0's node
230 For UMA systems that use FLATMEM memory model the 0's node
235 The page frame number of the starting page frame in this node.
238 Total number of physical pages present in this node.
244 A lock that protects the fields defining the node extents. Only defined when
252 The Node ID (NID) of the node, starts at 0.
255 This is a per-node reserve of pages that are not available to userspace
264 …Per-node queue of huge pages that their split was deferred. Defined only when ``CONFIG_TRANSPARENT…
267 Per-node lruvec holding LRU lists and related parameters. Used only when
277 Per-node instance of kswapd kernel thread.
322 Per-node instance of kcompactd kernel thread.
332 Per-CPU VM statistics for the node
335 VM statistics for the node.
342 which is an element of the ``node_zones`` array of the node it belongs to.
347 a memory allocation to determine the highest zone in a node from which the
351 node, the process continues up to and including the lowest zone. For example, if
352 a node contains ``ZONE_DMA32``, ``ZONE_NORMAL`` and ``ZONE_MOVABLE`` and the
398 as the node may be balanced overall and kswapd will not wake naturally.
422 ``node``
423 The index of the node this zone belongs to. Available only when
427 Pointer to the ``struct pglist_data`` of the node this zone belongs to.