Lines Matching +full:frame +full:- +full:number

1 .. SPDX-License-Identifier: GPL-2.0
29 Regardless of the selected memory model, there exists one-to-one
30 mapping between the physical page frame number (PFN) and the
41 non-NUMA systems with contiguous, or mostly contiguous, physical
62 straightforward: `PFN - ARCH_PFN_OFFSET` is an index to the
65 The `ARCH_PFN_OFFSET` defines the first page frame number for
77 `pg_data_t` is the number of the first page frame belonging to that
84 Every `node_mem_map` behaves exactly as FLATMEM's `mem_map` -
85 every physical page frame in a node has a `struct page` entry in the
87 `flags` field of the `struct page` encodes the node number of the
96 to convert PFN to the node number. The opposite conversion helper
97 :c:func:`page_to_nid` is generic as it uses the node number encoded in
98 page->flags.
100 Once the node number is known, the PFN can be used to index
110 as hot-plug and hot-remove of the physical memory, alternative memory
111 maps for non-volatile memory devices and deferred initialization of
118 that aids the sections management. The section size and maximal number
125 The maximal number of sections is denoted `NR_MEM_SECTIONS` and
130    NR\_MEM\_SECTIONS = 2 ^ {(MAX\_PHYSMEM\_BITS - SECTION\_SIZE\_BITS)}
132 The `mem_section` objects are arranged in a two-dimensional array
134 on `CONFIG_SPARSEMEM_EXTREME` and the maximal possible number of
142   `mem_section` objects and the number of rows is calculated to fit
152 corresponding `struct page` - a "classic sparse" and "sparse
156 The classic sparse encodes the section number of a page in page->flags
158 frame. Inside a section, the PFN is the index to the array of pages.
178 for persistent memory devices in pre-allocated storage on those
206 this lack of user-api constraint to allow sub-section sized memory
207 ranges to be specified to :c:func:`arch_add_memory`, the top-half of
208 memory hotplug. Sub-section support allows for 2MB as the cross-arch
213 * pmem: Map platform persistent memory to be used as a direct-I/O target
216 * hmm: Extend `ZONE_DEVICE` with `->page_fault()` and `->page_free()`
217   event callbacks to allow a device-driver to coordinate memory management
218   events related to device-memory, typically GPU memory. See
222   PCI/-E topology to coordinate direct-DMA operations between themselves,