Lines Matching full:memory
3 menu "Memory Management options"
10 prompt "Memory model"
17 Linux manages its memory internally. Most users will
22 bool "Flat Memory"
31 spaces and for features like NUMA and memory hotplug,
32 choose "Sparse Memory"
34 If unsure, choose this option (Flat Memory) over any other.
37 bool "Discontiguous Memory"
41 memory systems, over FLATMEM. These systems have holes
45 Although "Discontiguous Memory" is still used by several
47 "Sparse Memory".
49 If unsure, choose "Sparse Memory" over this option.
52 bool "Sparse Memory"
56 memory hot-plug systems. This is normal.
59 holes is their physical address space and allows memory
62 If unsure, choose "Flat Memory" over this option.
84 # to represent different areas of memory. This variable allows
121 bool "Sparse Memory virtual memmap"
146 # Only be set on architectures that have completely implemented memory hotplug
154 bool "Allow for memory hot-add"
163 bool "Online the newly added memory blocks by default"
166 This option sets the default policy setting for memory hotplug
167 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
168 determines what happens to newly added memory regions. Policy setting
170 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
172 Say Y here if you want all hot-plugged memory blocks to appear in
175 memory blocks in 'offline' state.
178 bool "Allow for memory hot remove"
203 # support for memory balloon
208 # support for memory balloon compaction
210 bool "Allow for balloon memory compaction/migration"
214 Memory fragmentation introduced by ballooning might reduce
215 significantly the number of 2MB contiguous memory blocks that can be
218 by the guest workload. Allowing the compaction & migration for memory
219 pages enlisted as being part of memory balloon devices avoids the
220 scenario aforementioned and helps improving memory defragmentation.
223 # support for memory compaction
225 bool "Allow for memory compaction"
230 Compaction is the only memory management component to form
231 high order (larger physically contiguous) memory blocks
234 invocations for high order memory requests. You shouldn't
272 the full range of memory available to the CPU. Enabled
297 saving memory until one or another app needs to modify the content.
308 This is the portion of low virtual memory which should be protected
328 bool "Enable recovery from hardware memory errors"
332 Enables code to recover from some memory failures on systems
334 even when some of its memory has uncorrected errors. This requires
335 special hardware support and typically ECC memory.
348 of memory on which to store mappings, but it can only ask the system
379 applications by speeding up page faults during memory
383 If memory constrained on embedded, you may want to say N.
396 memory footprint of applications without a guaranteed
405 memory footprint of applications without a guaranteed
440 memory. So when the PFRA "evicts" a page, it first attempts to use
442 "transcendent memory", memory that is not directly accessible or
448 When a transcendent memory driver is available (such as zcache or
449 Xen transcendent memory), a significant I/O reduction
462 "transcendent memory", memory that is not directly accessible or
464 time-varying size. When space in transcendent memory is available,
473 bool "Contiguous Memory Allocator"
478 This enables the Contiguous Memory Allocator which allows other
479 subsystems to allocate big physically-contiguous blocks of memory.
480 CMA reserves a region of memory and allows only movable pages to
481 be allocated from it. This way, the kernel can use the memory for
514 bool "Track memory changes"
518 This option enables memory changes tracking by introducing a
533 compress them into a dynamically allocated RAM-based memory pool.
539 v3.11) that interacts heavily with memory reclaim. While these
540 interactions don't cause any known issues on simple memory setups,
545 tristate "Common API for compressed memory storage"
547 Compressed memory storage API. This allows using either zbud or
569 tristate "Memory allocator for compressed pages"
572 zsmalloc is a slab-based memory allocator designed to store
573 compressed RAM pages. zsmalloc uses virtual memory mapping
613 arch). The stack will be located at the highest memory address minus
641 be useful to tune memory cgroup limits and/or for job placement
651 bool "Device memory (pmem, HMM, etc...) hotplug support"
659 Device memory hotplug support allows for establishing pmem,
660 or other device driver discovered memory regions, in the
680 bool "Unaddressable device memory (GPU memory, ...)"
686 memory; i.e., memory that is only accessible from the device (or
698 bool "Collect percpu memory statistics"
702 be used to help understand percpu memory usage.