Lines Matching full:that
12 however, that this range contains small holes that are not accessible
20 whether it is possible to manually override that default.
34 helpers that allow the conversion from PFN to `struct page` and vice
44 In the FLATMEM memory model, there is a global `mem_map` array that
52 usable until the call to :c:func:`memblock_free_all` that hands all
56 it may free parts of the `mem_map` array that do not cover the
75 things, `pg_data_t` holds the `node_mem_map` array that maps
76 physical pages belonging to that node. The `node_start_pfn` field of
77 `pg_data_t` is the number of the first page frame belonging to that
88 node hosting that page.
95 Architectures that support DISCONTIGMEM provide :c:func:`pfn_to_nid`
103 `node_start_pfn` is the PFN of that page.
109 is the only memory model that supports several advanced features such
116 that contains `section_mem_map` that is, logically, a pointer to an
118 that aids the sections management. The section size and maximal number
120 `MAX_PHYSMEM_BITS` constants defined by each architecture that
122 physical address that an architecture supports, the
157 and uses high bits of a PFN to access the section that maps that page
162 page *vmemmap` pointer that points to a virtually contiguous array of
163 `struct page` objects. A PFN is an index to that array and the the
164 offset of the `struct page` from `vmemmap` is the PFN of that
168 addresses that will map the physical pages containing the memory
169 map and make sure that `vmemmap` points to that range. In addition,
171 that will allocate the physical memory and create page tables for the
180 that is eventually passed to vmemmap_populate() through a long chain
190 that the page objects for these address ranges are never marked online,
191 and that a reference must be taken against the device, not just the page
198 for back referencing to the host device / driver that mapped the memory.
202 for smaller granularity of populating the `mem_map`. Given that