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
51 usable until the call to :c:func:`memblock_free_all` that hands all the
55 it may free parts of the `mem_map` array that do not cover the
74 things, `pg_data_t` holds the `node_mem_map` array that maps
75 physical pages belonging to that node. The `node_start_pfn` field of
76 `pg_data_t` is the number of the first page frame belonging to that
87 node hosting that page.
94 Architectures that support DISCONTIGMEM provide :c:func:`pfn_to_nid`
102 `node_start_pfn` is the PFN of that page.
108 is the only memory model that supports several advanced features such
115 that contains `section_mem_map` that is, logically, a pointer to an
117 that aids the sections management. The section size and maximal number
119 `MAX_PHYSMEM_BITS` constants defined by each architecture that
121 physical address that an architecture supports, the
153 and uses high bits of a PFN to access the section that maps that page
158 page *vmemmap` pointer that points to a virtually contiguous array of
159 `struct page` objects. A PFN is an index to that array and the
160 offset of the `struct page` from `vmemmap` is the PFN of that
164 addresses that will map the physical pages containing the memory
165 map and make sure that `vmemmap` points to that range. In addition,
167 that will allocate the physical memory and create page tables for the
176 that is eventually passed to vmemmap_populate() through a long chain
186 that the page objects for these address ranges are never marked online,
187 and that a reference must be taken against the device, not just the page
194 for back referencing to the host device / driver that mapped the memory.
198 for smaller granularity of populating the `mem_map`. Given that