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.
71 MEMORY_MONITOR is a monitor of some memory reclaim method.
88 Add more attributes in memory cgroup, these attribute is used
89 to show information, shrink memory, swapin page and so on.
108 bool "Memory reclaim delay accounting"
111 Memory reclaim delay accounting. Never use it as a kernel module.
131 # to represent different areas of memory. This variable allows
164 bool "Sparse Memory virtual memmap"
182 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
183 # after early boot, so it can still be used to test for validity of memory.
184 # Also, memblocks are updated with memory hot(un)plug.
196 # Only be set on architectures that have completely implemented memory hotplug
204 bool "Allow for memory hot-add"
216 bool "Online the newly added memory blocks by default"
219 This option sets the default policy setting for memory hotplug
220 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
221 determines what happens to newly added memory regions. Policy setting
223 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
225 Say Y here if you want all hot-plugged memory blocks to appear in
228 memory blocks in 'offline' state.
231 bool "Allow for memory hot remove"
259 # support for memory balloon
264 # support for memory balloon compaction
266 bool "Allow for balloon memory compaction/migration"
270 Memory fragmentation introduced by ballooning might reduce
271 significantly the number of 2MB contiguous memory blocks that can be
274 by the guest workload. Allowing the compaction & migration for memory
275 pages enlisted as being part of memory balloon devices avoids the
276 scenario aforementioned and helps improving memory defragmentation.
279 # support for memory compaction
281 bool "Allow for memory compaction"
286 Compaction is the only memory management component to form
287 high order (larger physically contiguous) memory blocks
290 invocations for high order memory requests. You shouldn't
304 memory can be freed within the host for other uses.
339 the full range of memory available to the CPU. Enabled
365 saving memory until one or another app needs to modify the content.
376 This is the portion of low virtual memory which should be protected
396 bool "Enable recovery from hardware memory errors"
400 Enables code to recover from some memory failures on systems
402 even when some of its memory has uncorrected errors. This requires
403 special hardware support and typically ECC memory.
416 of memory on which to store mappings, but it can only ask the system
447 applications by speeding up page faults during memory
451 If memory constrained on embedded, you may want to say N.
464 memory footprint of applications without a guaranteed
473 memory footprint of applications without a guaranteed
504 memory. So when the PFRA "evicts" a page, it first attempts to use
506 "transcendent memory", memory that is not directly accessible or
512 When a transcendent memory driver is available (such as zcache or
513 Xen transcendent memory), a significant I/O reduction
526 "transcendent memory", memory that is not directly accessible or
528 time-varying size. When space in transcendent memory is available,
537 bool "Contiguous Memory Allocator"
542 This enables the Contiguous Memory Allocator which allows other
543 subsystems to allocate big physically-contiguous blocks of memory.
544 CMA reserves a region of memory and allows only movable pages to
545 be allocated from it. This way, the kernel can use the memory for
589 bool "Track memory changes"
593 This option enables memory changes tracking by introducing a
607 compress them into a dynamically allocated RAM-based memory pool.
613 v3.11) that interacts heavily with memory reclaim. While these
614 interactions don't cause any known issues on simple memory setups,
736 tristate "Common API for compressed memory storage"
738 Compressed memory storage API. This allows using either zbud or
760 tristate "Memory allocator for compressed pages"
763 zsmalloc is a slab-based memory allocator designed to store
764 compressed RAM pages. zsmalloc uses virtual memory mapping
791 arch). The stack will be located at the highest memory address minus
819 be useful to tune memory cgroup limits and/or for job placement
829 bool "Device memory (pmem, HMM, etc...) hotplug support"
837 Device memory hotplug support allows for establishing pmem,
838 or other device driver discovered memory regions, in the
857 bool "Unaddressable device memory (GPU memory, ...)"
863 memory; i.e., memory that is only accessible from the device (or
878 bool "Collect percpu memory statistics"
882 be used to help understand percpu memory usage.
927 Allow naming anonymous virtual memory areas.
929 This feature allows assigning names to virtual memory areas. Assigned
931 and help identifying individual anonymous memory areas.
932 Assigning a name to anonymous virtual memory area might prevent that
933 area from being merged with adjacent virtual memory areas due to the
939 bool "Low Memory Killer"
945 bool "Low Memory Killer Debug"
970 bool "Purgeable memory feature"
978 bool "Purgeable memory debug"
982 Debug info for purgeable memory
985 bool "Purgeable memory feature for ashmem"