Lines Matching full:memory

6 Physical Memory Model
9 Physical memory in a system may be addressed in different ways. The
10 simplest case is when the physical memory starts at address 0 and
15 different memory banks are attached to different CPUs.
17 Linux abstracts this diversity using one of the three memory models:
19 memory models it supports, what the default memory model is and
26 All the memory models track the status of physical page frames using
29 Regardless of the selected memory model, there exists one-to-one
33 Each memory model defines :c:func:`pfn_to_page` and :c:func:`page_to_pfn`
40 The simplest memory model is FLATMEM. This model is suitable for
42 memory.
44 In the FLATMEM memory model, there is a global `mem_map` array that
45 maps the entire physical memory. For most architectures, the holes
52 memory to the page allocator.
64 systems with physical memory starting at address different from 0.
69 The DISCONTIGMEM model treats the physical memory as a collection of
71 constructs an independent memory management subsystem represented by
106 SPARSEMEM is the most versatile memory model available in Linux and it
107 is the only memory model that supports several advanced features such
108 as hot-plug and hot-remove of the physical memory, alternative memory
109 maps for non-volatile memory devices and deferred initialization of
110 the memory map for larger systems.
112 The SPARSEMEM model presents the physical memory as a collection of
141   all the memory sections.
144 initialize the memory sections and the memory maps.
155 The sparse vmemmap uses a virtually mapped memory map to optimize
163 addresses that will map the physical pages containing the memory
166 that will allocate the physical memory and create page tables for the
167 virtual memory map. If an architecture does not have any special
169 :c:func:`vmemmap_populate_basepages` provided by the generic memory
172 The virtually mapped memory map allows storing `struct page` objects
173 for persistent memory devices in pre-allocated storage on those
178 allocate memory map on the persistent memory device.
187 to keep the memory pinned for active use. `ZONE_DEVICE`, via
188 :c:func:`devm_memremap_pages`, performs just enough memory hotplug to
192 free memory and the page's `struct list_head lru` space is repurposed
193 for back referencing to the host device / driver that mapped the memory.
195 While `SPARSEMEM` presents memory as a collection of sections,
196 optionally collected into memory blocks, `ZONE_DEVICE` users have a need
198 `ZONE_DEVICE` memory is never marked online it is subsequently never
199 subject to its memory ranges being exposed through the sysfs memory
200 hotplug api on memory block boundaries. The implementation relies on
201 this lack of user-api constraint to allow sub-section sized memory
203 memory hotplug. Sub-section support allows for 2MB as the cross-arch
208 * pmem: Map platform persistent memory to be used as a direct-I/O target
212   event callbacks to allow a device-driver to coordinate memory management
213   events related to device-memory, typically GPU memory. See
218   i.e. bypass host memory.