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.
160 zsmalloc is a slab-based memory allocator designed to store
203 bool "Configure for minimal memory footprint"
207 Configures the slab allocator in a way to achieve minimal memory
219 For reduced kernel memory fragmentation, slab caches can be
257 memory fragmentation, though in practice it's only a handful
295 vulnerable memory objects on the heap for the purpose of exploiting
296 memory vulnerabilities.
299 that effectively diverges the memory objects allocated for different
301 limited degree of memory and CPU overhead that relates to hardware and
311 utilization of a direct-mapped memory-side-cache. See section
312 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI
314 the presence of a memory-side-cache. There are also incidental
342 bool "Allow mmapped anonymous memory to be uninitialized"
346 Normally, and according to the Linux spec, anonymous memory obtained
368 prompt "Memory model"
374 Linux manages its memory internally. Most users will
379 bool "Flat Memory"
388 spaces and for features like NUMA and memory hotplug,
389 choose "Sparse Memory".
391 If unsure, choose this option (Flat Memory) over any other.
394 bool "Sparse Memory"
398 memory hot-plug systems. This is normal.
401 holes is their physical address space and allows memory
404 If unsure, choose "Flat Memory" over this option.
442 bool "Sparse Memory virtual memmap"
472 # Enable memblock support for scratch memory which is needed for kexec handover
476 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
477 # after early boot, so it can still be used to test for validity of memory.
478 # Also, memblocks are updated with memory hot(un)plug.
497 # Only be set on architectures that have completely implemented memory hotplug
511 bool "Memory hotplug"
521 prompt "Memory Hotplug Default Online Type"
524 Default memory type for hotplugged memory.
526 This option sets the default policy setting for memory hotplug
527 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
528 determines what happens to newly added memory regions. Policy setting
535 Select online_kernel to generally allow kernel usage of this memory.
536 Select online_movable to generally disallow kernel usage of this memory.
540 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
545 Hotplugged memory will not be onlined by default.
547 handle onlining of hotplug memory policy.
553 hotplugged memory into the zone it thinks is reasonable.
554 This memory may be utilized for kernel data.
560 hotplugged memory into a zone capable of being used for kernel
567 hotplug memory into ZONE_MOVABLE. This memory will generally
571 ZONE_NORMAL memory is available to describe hotplug memory,
572 otherwise hotplug memory may fail to online. For example,
573 sufficient kernel-capable memory (ZONE_NORMAL) must be
579 bool "Allow for memory hot remove"
622 # support for memory balloon
627 # support for memory balloon compaction
629 bool "Allow for balloon memory compaction/migration"
633 Memory fragmentation introduced by ballooning might reduce
634 significantly the number of 2MB contiguous memory blocks that can be
637 by the guest workload. Allowing the compaction & migration for memory
638 pages enlisted as being part of memory balloon devices avoids the
639 scenario aforementioned and helps improving memory defragmentation.
642 # support for memory compaction
644 bool "Allow for memory compaction"
649 Compaction is the only memory management component to form
650 high order (larger physically contiguous) memory blocks
653 invocations for high order memory requests. You shouldn't
672 memory can be freed within the host for other uses.
731 memory available to the CPU. Enabled by default when HIGHMEM is
747 saving memory until one or another app needs to modify the content.
758 This is the portion of low virtual memory which should be protected
778 bool "Enable recovery from hardware memory errors"
782 Enables code to recover from some memory failures on systems
784 even when some of its memory has uncorrected errors. This requires
785 special hardware support and typically ECC memory.
798 of memory on which to store mappings, but it can only ask the system
839 applications by speeding up page faults during memory
843 If memory constrained on embedded, you may want to say N.
858 memory footprint of applications without a guaranteed
867 memory footprint of applications without a guaranteed
964 bool "Contiguous Memory Allocator"
969 This enables the Contiguous Memory Allocator which allows other
970 subsystems to allocate big physically-contiguous blocks of memory.
971 CMA reserves a region of memory and allows only movable pages to
972 be allocated from it. This way, the kernel can use the memory for
1039 bool "Track memory changes"
1043 This option enables memory changes tracking by introducing a
1096 be useful to tune memory cgroup limits and/or for job placement
1133 bool "Device memory (pmem, HMM, etc...) hotplug support"
1140 Device memory hotplug support allows for establishing pmem,
1141 or other device driver discovered memory regions, in the
1160 bool "Unaddressable device memory (GPU memory, ...)"
1166 memory; i.e., memory that is only accessible from the device (or
1192 bool "Collect percpu memory statistics"
1196 be used to help understand percpu memory usage.
1254 memory areas visible only in the context of the owning process and
1262 Allow naming anonymous virtual memory areas.
1264 This feature allows assigning names to virtual memory areas. Assigned
1266 and help identifying individual anonymous memory areas.
1267 Assigning a name to anonymous virtual memory area might prevent that
1268 area from being merged with adjacent virtual memory areas due to the
1297 file-backed memory types like shmem and hugetlbfs.
1307 A high performance LRU implementation to overcommit memory. See
1323 This option has a per-memcg and per-node memory overhead.
1339 This feature allows locking each virtual memory area separately when