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 prompt "Memory Hotplug Default Online Type"
557 Default memory type for hotplugged memory.
559 This option sets the default policy setting for memory hotplug
560 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
561 determines what happens to newly added memory regions. Policy setting
568 Select online_kernel to generally allow kernel usage of this memory.
569 Select online_movable to generally disallow kernel usage of this memory.
573 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
578 Hotplugged memory will not be onlined by default.
580 handle onlining of hotplug memory policy.
586 hotplugged memory into the zone it thinks is reasonable.
587 This memory may be utilized for kernel data.
593 hotplugged memory into a zone capable of being used for kernel
600 hotplug memory into ZONE_MOVABLE. This memory will generally
604 ZONE_NORMAL memory is available to describe hotplug memory,
605 otherwise hotplug memory may fail to online. For example,
606 sufficient kernel-capable memory (ZONE_NORMAL) must be
612 bool "Allow for memory hot remove"
655 # support for memory balloon
660 # support for memory balloon compaction
662 bool "Allow for balloon memory compaction/migration"
666 Memory fragmentation introduced by ballooning might reduce
667 significantly the number of 2MB contiguous memory blocks that can be
670 by the guest workload. Allowing the compaction & migration for memory
671 pages enlisted as being part of memory balloon devices avoids the
672 scenario aforementioned and helps improving memory defragmentation.
675 # support for memory compaction
677 bool "Allow for memory compaction"
682 Compaction is the only memory management component to form
683 high order (larger physically contiguous) memory blocks
686 invocations for high order memory requests. You shouldn't
705 memory can be freed within the host for other uses.
764 memory available to the CPU. Enabled by default when HIGHMEM is
780 saving memory until one or another app needs to modify the content.
791 This is the portion of low virtual memory which should be protected
811 bool "Enable recovery from hardware memory errors"
815 Enables code to recover from some memory failures on systems
817 even when some of its memory has uncorrected errors. This requires
818 special hardware support and typically ECC memory.
831 of memory on which to store mappings, but it can only ask the system
868 applications by speeding up page faults during memory
872 If memory constrained on embedded, you may want to say N.
887 memory footprint of applications without a guaranteed
896 memory footprint of applications without a guaranteed
969 bool "Contiguous Memory Allocator"
974 This enables the Contiguous Memory Allocator which allows other
975 subsystems to allocate big physically-contiguous blocks of memory.
976 CMA reserves a region of memory and allows only movable pages to
977 be allocated from it. This way, the kernel can use the memory for
1009 bool "Track memory changes"
1013 This option enables memory changes tracking by introducing a
1066 be useful to tune memory cgroup limits and/or for job placement
1106 bool "Device memory (pmem, HMM, etc...) hotplug support"
1114 Device memory hotplug support allows for establishing pmem,
1115 or other device driver discovered memory regions, in the
1134 bool "Unaddressable device memory (GPU memory, ...)"
1140 memory; i.e., memory that is only accessible from the device (or
1166 bool "Collect percpu memory statistics"
1170 be used to help understand percpu memory usage.
1232 memory areas visible only in the context of the owning process and
1240 Allow naming anonymous virtual memory areas.
1242 This feature allows assigning names to virtual memory areas. Assigned
1244 and help identifying individual anonymous memory areas.
1245 Assigning a name to anonymous virtual memory area might prevent that
1246 area from being merged with adjacent virtual memory areas due to the
1275 file-backed memory types like shmem and hugetlbfs.
1285 A high performance LRU implementation to overcommit memory. See
1301 This option has a per-memcg and per-node memory overhead.
1317 This feature allows locking each virtual memory area separately when