Lines Matching full:memory
3 menu "Memory Management options"
16 bool "Support for paging of anonymous memory (swap)"
22 used to provide more virtual memory than the actual RAM present
33 compress them into a dynamically allocated RAM-based memory pool.
49 bool "Shrink the zswap pool on memory pressure"
55 written back to the backing swap device) on memory pressure.
60 and consume memory indefinitely.
207 zsmalloc is a slab-based memory allocator designed to store
246 bool "Configure for minimal memory footprint"
250 Configures the slab allocator in a way to achieve minimal memory
262 For reduced kernel memory fragmentation, slab caches can be
300 memory fragmentation, though in practice it's only a handful
338 vulnerable memory objects on the heap for the purpose of exploiting
339 memory vulnerabilities.
342 that effectively diverges the memory objects allocated for different
344 limited degree of memory and CPU overhead that relates to hardware and
354 utilization of a direct-mapped memory-side-cache. See section
355 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI
357 the presence of a memory-side-cache. There are also incidental
385 bool "Allow mmapped anonymous memory to be uninitialized"
389 Normally, and according to the Linux spec, anonymous memory obtained
411 prompt "Memory model"
417 Linux manages its memory internally. Most users will
422 bool "Flat Memory"
431 spaces and for features like NUMA and memory hotplug,
432 choose "Sparse Memory".
434 If unsure, choose this option (Flat Memory) over any other.
437 bool "Sparse Memory"
441 memory hot-plug systems. This is normal.
444 holes is their physical address space and allows memory
447 If unsure, choose "Flat Memory" over this option.
485 bool "Sparse Memory virtual memmap"
509 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
510 # after early boot, so it can still be used to test for validity of memory.
511 # Also, memblocks are updated with memory hot(un)plug.
530 # Only be set on architectures that have completely implemented memory hotplug
544 bool "Memory hotplug"
554 bool "Online the newly added memory blocks by default"
557 This option sets the default policy setting for memory hotplug
558 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
559 determines what happens to newly added memory regions. Policy setting
561 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
563 Say Y here if you want all hot-plugged memory blocks to appear in
566 memory blocks in 'offline' state.
569 bool "Allow for memory hot remove"
612 # support for memory balloon
617 # support for memory balloon compaction
619 bool "Allow for balloon memory compaction/migration"
623 Memory fragmentation introduced by ballooning might reduce
624 significantly the number of 2MB contiguous memory blocks that can be
627 by the guest workload. Allowing the compaction & migration for memory
628 pages enlisted as being part of memory balloon devices avoids the
629 scenario aforementioned and helps improving memory defragmentation.
632 # support for memory compaction
634 bool "Allow for memory compaction"
639 Compaction is the only memory management component to form
640 high order (larger physically contiguous) memory blocks
643 invocations for high order memory requests. You shouldn't
662 memory can be freed within the host for other uses.
721 memory available to the CPU. Enabled by default when HIGHMEM is
737 saving memory until one or another app needs to modify the content.
748 This is the portion of low virtual memory which should be protected
768 bool "Enable recovery from hardware memory errors"
772 Enables code to recover from some memory failures on systems
774 even when some of its memory has uncorrected errors. This requires
775 special hardware support and typically ECC memory.
788 of memory on which to store mappings, but it can only ask the system
825 applications by speeding up page faults during memory
829 If memory constrained on embedded, you may want to say N.
844 memory footprint of applications without a guaranteed
853 memory footprint of applications without a guaranteed
926 bool "Contiguous Memory Allocator"
931 This enables the Contiguous Memory Allocator which allows other
932 subsystems to allocate big physically-contiguous blocks of memory.
933 CMA reserves a region of memory and allows only movable pages to
934 be allocated from it. This way, the kernel can use the memory for
966 bool "Track memory changes"
970 This option enables memory changes tracking by introducing a
1023 be useful to tune memory cgroup limits and/or for job placement
1063 bool "Device memory (pmem, HMM, etc...) hotplug support"
1071 Device memory hotplug support allows for establishing pmem,
1072 or other device driver discovered memory regions, in the
1091 bool "Unaddressable device memory (GPU memory, ...)"
1097 memory; i.e., memory that is only accessible from the device (or
1123 bool "Collect percpu memory statistics"
1127 be used to help understand percpu memory usage.
1189 memory areas visible only in the context of the owning process and
1197 Allow naming anonymous virtual memory areas.
1199 This feature allows assigning names to virtual memory areas. Assigned
1201 and help identifying individual anonymous memory areas.
1202 Assigning a name to anonymous virtual memory area might prevent that
1203 area from being merged with adjacent virtual memory areas due to the
1232 file-backed memory types like shmem and hugetlbfs.
1242 A high performance LRU implementation to overcommit memory. See
1258 This option has a per-memcg and per-node memory overhead.
1274 This feature allows locking each virtual memory area separately when