Lines Matching full:memory
3 menu "Memory Management options"
13 bool "Support for paging of anonymous memory (swap)"
19 used to provide more virtual memory than the actual RAM present
30 compress them into a dynamically allocated RAM-based memory pool.
46 bool "Shrink the zswap pool on memory pressure"
52 written back to the backing swap device) on memory pressure.
57 and consume memory indefinitely.
177 bool "Configure for minimal memory footprint"
181 Configures the slab allocator in a way to achieve minimal memory
193 For reduced kernel memory fragmentation, slab caches can be
231 memory fragmentation, though in practice it's only a handful
269 vulnerable memory objects on the heap for the purpose of exploiting
270 memory vulnerabilities.
273 that effectively diverges the memory objects allocated for different
275 limited degree of memory and CPU overhead that relates to hardware and
285 utilization of a direct-mapped memory-side-cache. See section
286 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI
288 the presence of a memory-side-cache. There are also incidental
316 bool "Allow mmapped anonymous memory to be uninitialized"
320 Normally, and according to the Linux spec, anonymous memory obtained
342 prompt "Memory model"
348 Linux manages its memory internally. Most users will
353 bool "Flat Memory"
362 spaces and for features like NUMA and memory hotplug,
363 choose "Sparse Memory".
365 If unsure, choose this option (Flat Memory) over any other.
368 bool "Sparse Memory"
372 memory hot-plug systems. This is normal.
375 holes is their physical address space and allows memory
378 If unsure, choose "Flat Memory" over this option.
445 # Enable memblock support for scratch memory which is needed for kexec handover
449 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
450 # after early boot, so it can still be used to test for validity of memory.
451 # Also, memblocks are updated with memory hot(un)plug.
470 # Only be set on architectures that have completely implemented memory hotplug
484 bool "Memory hotplug"
494 prompt "Memory Hotplug Default Online Type"
497 Default memory type for hotplugged memory.
499 This option sets the default policy setting for memory hotplug
500 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
501 determines what happens to newly added memory regions. Policy setting
508 Select online_kernel to generally allow kernel usage of this memory.
509 Select online_movable to generally disallow kernel usage of this memory.
513 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
518 Hotplugged memory will not be onlined by default.
520 handle onlining of hotplug memory policy.
526 hotplugged memory into the zone it thinks is reasonable.
527 This memory may be utilized for kernel data.
533 hotplugged memory into a zone capable of being used for kernel
540 hotplug memory into ZONE_MOVABLE. This memory will generally
544 ZONE_NORMAL memory is available to describe hotplug memory,
545 otherwise hotplug memory may fail to online. For example,
546 sufficient kernel-capable memory (ZONE_NORMAL) must be
552 bool "Allow for memory hot remove"
595 # support for memory balloon
600 # support for memory balloon compaction
602 bool "Allow for balloon memory compaction/migration"
606 Memory fragmentation introduced by ballooning might reduce
607 significantly the number of 2MB contiguous memory blocks that can be
610 by the guest workload. Allowing the compaction & migration for memory
611 pages enlisted as being part of memory balloon devices avoids the
612 scenario aforementioned and helps improving memory defragmentation.
615 # support for memory compaction
617 bool "Allow for memory compaction"
622 Compaction is the only memory management component to form
623 high order (larger physically contiguous) memory blocks
626 invocations for high order memory requests. You shouldn't
645 memory can be freed within the host for other uses.
711 saving memory until one or another app needs to modify the content.
722 This is the portion of low virtual memory which should be protected
742 bool "Enable recovery from hardware memory errors"
745 Enables code to recover from some memory failures on systems
747 even when some of its memory has uncorrected errors. This requires
748 special hardware support and typically ECC memory.
761 of memory on which to store mappings, but it can only ask the system
796 from access to large folios for zeroing memory.
799 once and never freed. One full huge page's worth of memory shall
802 Say Y if your system has lots of memory. Say N if you are
803 memory constrained.
818 applications by speeding up page faults during memory
822 If memory constrained on embedded, you may want to say N.
837 memory footprint of applications without a guaranteed
846 memory footprint of applications without a guaranteed
881 increase the memory footprint of applications without a
926 increase the memory footprint of applications without a
1044 bool "Contiguous Memory Allocator"
1049 This enables the Contiguous Memory Allocator which allows other
1050 subsystems to allocate big physically-contiguous blocks of memory.
1051 CMA reserves a region of memory and allows only movable pages to
1052 be allocated from it. This way, the kernel can use the memory for
1119 bool "Track memory changes"
1123 This option enables memory changes tracking by introducing a
1176 be useful to tune memory cgroup limits and/or for job placement
1213 bool "Device memory (pmem, HMM, etc...) hotplug support"
1220 Device memory hotplug support allows for establishing pmem,
1221 or other device driver discovered memory regions, in the
1240 bool "Unaddressable device memory (GPU memory, ...)"
1246 memory; i.e., memory that is only accessible from the device (or
1272 bool "Collect percpu memory statistics"
1276 be used to help understand percpu memory usage.
1334 memory areas visible only in the context of the owning process and
1342 Allow naming anonymous virtual memory areas.
1344 This feature allows assigning names to virtual memory areas. Assigned
1346 and help identifying individual anonymous memory areas.
1347 Assigning a name to anonymous virtual memory area might prevent that
1348 area from being merged with adjacent virtual memory areas due to the
1377 file-backed memory types like shmem and hugetlbfs.
1387 A high performance LRU implementation to overcommit memory. See
1403 This option has a per-memcg and per-node memory overhead.
1419 This feature allows locking each virtual memory area separately when