Lines Matching full:page

20 All the memory models track the status of physical page frames using
21 struct page arranged in one or more arrays.
24 mapping between the physical page frame number (PFN) and the
25 corresponding `struct page`.
28 helpers that allow the conversion from PFN to `struct page` and vice
40 have entries in the `mem_map` array. The `struct page` objects
46 memory to the page allocator.
53 With FLATMEM, the conversion between a PFN and the `struct page` is
57 The `ARCH_PFN_OFFSET` defines the first page frame number for
104 corresponding `struct page` - a "classic sparse" and "sparse
108 The classic sparse encodes the section number of a page in page->flags
109 and uses high bits of a PFN to access the section that maps that page
114 page *vmemmap` pointer that points to a virtually contiguous array of
115 `struct page` objects. A PFN is an index to that array and the
116 offset of the `struct page` from `vmemmap` is the PFN of that
117 page.
123 that will allocate the physical memory and create page tables for the
129 The virtually mapped memory map allows storing `struct page` objects
140 `struct page` `mem_map` services for device driver identified physical
142 that the page objects for these address ranges are never marked online,
143 and that a reference must be taken against the device, not just the page
148 page reference count never drops below 1 the page is never tracked as
149 free memory and the page's `struct list_head lru` space is repurposed
173 * p2pdma: Create `struct page` objects to allow peer devices in a