Lines Matching full:memory
3 menu "Memory Management options"
10 prompt "Memory model"
16 Linux manages its memory internally. Most users will
21 bool "Flat Memory"
30 spaces and for features like NUMA and memory hotplug,
31 choose "Sparse Memory".
33 If unsure, choose this option (Flat Memory) over any other.
36 bool "Sparse Memory"
40 memory hot-plug systems. This is normal.
43 holes is their physical address space and allows memory
46 If unsure, choose "Flat Memory" over this option.
84 bool "Sparse Memory virtual memmap"
99 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
100 # after early boot, so it can still be used to test for validity of memory.
101 # Also, memblocks are updated with memory hot(un)plug.
113 # Only be set on architectures that have completely implemented memory hotplug
124 bool "Allow for memory hot-add"
136 bool "Online the newly added memory blocks by default"
139 This option sets the default policy setting for memory hotplug
140 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
141 determines what happens to newly added memory regions. Policy setting
143 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
145 Say Y here if you want all hot-plugged memory blocks to appear in
148 memory blocks in 'offline' state.
154 bool "Allow for memory hot remove"
187 # support for memory balloon
192 # support for memory balloon compaction
194 bool "Allow for balloon memory compaction/migration"
198 Memory fragmentation introduced by ballooning might reduce
199 significantly the number of 2MB contiguous memory blocks that can be
202 by the guest workload. Allowing the compaction & migration for memory
203 pages enlisted as being part of memory balloon devices avoids the
204 scenario aforementioned and helps improving memory defragmentation.
207 # support for memory compaction
209 bool "Allow for memory compaction"
214 Compaction is the only memory management component to form
215 high order (larger physically contiguous) memory blocks
218 invocations for high order memory requests. You shouldn't
232 memory can be freed within the host for other uses.
274 memory available to the CPU. Enabled by default when HIGHMEM is
299 saving memory until one or another app needs to modify the content.
310 This is the portion of low virtual memory which should be protected
330 bool "Enable recovery from hardware memory errors"
334 Enables code to recover from some memory failures on systems
336 even when some of its memory has uncorrected errors. This requires
337 special hardware support and typically ECC memory.
350 of memory on which to store mappings, but it can only ask the system
381 applications by speeding up page faults during memory
385 If memory constrained on embedded, you may want to say N.
398 memory footprint of applications without a guaranteed
407 memory footprint of applications without a guaranteed
438 memory. So when the PFRA "evicts" a page, it first attempts to use
440 "transcendent memory", memory that is not directly accessible or
446 When a transcendent memory driver is available (such as zcache or
447 Xen transcendent memory), a significant I/O reduction
460 "transcendent memory", memory that is not directly accessible or
462 time-varying size. When space in transcendent memory is available,
471 bool "Contiguous Memory Allocator"
476 This enables the Contiguous Memory Allocator which allows other
477 subsystems to allocate big physically-contiguous blocks of memory.
478 CMA reserves a region of memory and allows only movable pages to
479 be allocated from it. This way, the kernel can use the memory for
520 bool "Track memory changes"
524 This option enables memory changes tracking by introducing a
538 compress them into a dynamically allocated RAM-based memory pool.
544 v3.11) that interacts heavily with memory reclaim. While these
545 interactions don't cause any known issues on simple memory setups,
667 tristate "Common API for compressed memory storage"
669 Compressed memory storage API. This allows using either zbud or
692 tristate "Memory allocator for compressed pages"
695 zsmalloc is a slab-based memory allocator designed to store
696 compressed RAM pages. zsmalloc uses virtual memory mapping
757 be useful to tune memory cgroup limits and/or for job placement
782 bool "Device memory (pmem, HMM, etc...) hotplug support"
790 Device memory hotplug support allows for establishing pmem,
791 or other device driver discovered memory regions, in the
810 bool "Unaddressable device memory (GPU memory, ...)"
816 memory; i.e., memory that is only accessible from the device (or
828 bool "Collect percpu memory statistics"
832 be used to help understand percpu memory usage.