Blame view
mm/Kconfig
27.5 KB
ec8f24b7f treewide: Add SPD... |
1 |
# SPDX-License-Identifier: GPL-2.0-only |
59e0b520c kconfig: add a Me... |
2 3 |
menu "Memory Management options" |
e1785e85b [PATCH] mm/Kconfi... |
4 5 |
config SELECT_MEMORY_MODEL def_bool y |
a8826eeb7 mm: remove depend... |
6 |
depends on ARCH_SELECT_MEMORY_MODEL |
e1785e85b [PATCH] mm/Kconfi... |
7 |
|
3a9da7655 [PATCH] create mm... |
8 9 |
choice prompt "Memory model" |
e1785e85b [PATCH] mm/Kconfi... |
10 11 |
depends on SELECT_MEMORY_MODEL default DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT |
d41dee369 [PATCH] sparsemem... |
12 |
default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT |
e1785e85b [PATCH] mm/Kconfi... |
13 |
default FLATMEM_MANUAL |
d66d109d3 mm/Kconfig: updat... |
14 15 16 17 18 |
help This option allows you to change some of the ways that Linux manages its memory internally. Most users will only have one option here selected by the architecture configuration. This is normal. |
3a9da7655 [PATCH] create mm... |
19 |
|
e1785e85b [PATCH] mm/Kconfi... |
20 |
config FLATMEM_MANUAL |
3a9da7655 [PATCH] create mm... |
21 |
bool "Flat Memory" |
c898ec16e [PATCH] allow fla... |
22 |
depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE |
3a9da7655 [PATCH] create mm... |
23 |
help |
d66d109d3 mm/Kconfig: updat... |
24 25 26 27 28 29 30 |
This option is best suited for non-NUMA systems with flat address space. The FLATMEM is the most efficient system in terms of performance and resource consumption and it is the best option for smaller systems. For systems that have holes in their physical address spaces and for features like NUMA and memory hotplug, |
dd33d29a1 mm/Kconfig: fix t... |
31 |
choose "Sparse Memory". |
d41dee369 [PATCH] sparsemem... |
32 33 |
If unsure, choose this option (Flat Memory) over any other. |
3a9da7655 [PATCH] create mm... |
34 |
|
e1785e85b [PATCH] mm/Kconfi... |
35 |
config DISCONTIGMEM_MANUAL |
f3519f919 [PATCH] fix mm/Kc... |
36 |
bool "Discontiguous Memory" |
3a9da7655 [PATCH] create mm... |
37 38 |
depends on ARCH_DISCONTIGMEM_ENABLE help |
785dcd44b [PATCH] mm/Kconfi... |
39 40 41 |
This option provides enhanced support for discontiguous memory systems, over FLATMEM. These systems have holes in their physical address spaces, and this option provides |
d66d109d3 mm/Kconfig: updat... |
42 |
more efficient handling of these holes. |
785dcd44b [PATCH] mm/Kconfi... |
43 |
|
d66d109d3 mm/Kconfig: updat... |
44 45 46 |
Although "Discontiguous Memory" is still used by several architectures, it is considered deprecated in favor of "Sparse Memory". |
785dcd44b [PATCH] mm/Kconfi... |
47 |
|
d66d109d3 mm/Kconfig: updat... |
48 |
If unsure, choose "Sparse Memory" over this option. |
3a9da7655 [PATCH] create mm... |
49 |
|
d41dee369 [PATCH] sparsemem... |
50 51 52 53 54 |
config SPARSEMEM_MANUAL bool "Sparse Memory" depends on ARCH_SPARSEMEM_ENABLE help This will be the only option for some systems, including |
d66d109d3 mm/Kconfig: updat... |
55 |
memory hot-plug systems. This is normal. |
d41dee369 [PATCH] sparsemem... |
56 |
|
d66d109d3 mm/Kconfig: updat... |
57 58 59 |
This option provides efficient support for systems with holes is their physical address space and allows memory hot-plug and hot-remove. |
d41dee369 [PATCH] sparsemem... |
60 |
|
d66d109d3 mm/Kconfig: updat... |
61 |
If unsure, choose "Flat Memory" over this option. |
d41dee369 [PATCH] sparsemem... |
62 |
|
3a9da7655 [PATCH] create mm... |
63 |
endchoice |
e1785e85b [PATCH] mm/Kconfi... |
64 65 66 |
config DISCONTIGMEM def_bool y depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL |
d41dee369 [PATCH] sparsemem... |
67 68 |
config SPARSEMEM def_bool y |
1a83e175d mm: fix sparsemem... |
69 |
depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL |
d41dee369 [PATCH] sparsemem... |
70 |
|
e1785e85b [PATCH] mm/Kconfi... |
71 72 |
config FLATMEM def_bool y |
d41dee369 [PATCH] sparsemem... |
73 74 75 76 77 |
depends on (!DISCONTIGMEM && !SPARSEMEM) || FLATMEM_MANUAL config FLAT_NODE_MEM_MAP def_bool y depends on !SPARSEMEM |
e1785e85b [PATCH] mm/Kconfi... |
78 |
|
93b7504e3 [PATCH] Introduce... |
79 80 81 82 83 84 85 86 |
# # Both the NUMA code and DISCONTIGMEM use arrays of pg_data_t's # to represent different areas of memory. This variable allows # those dependencies to exist individually. # config NEED_MULTIPLE_NODES def_bool y depends on DISCONTIGMEM || NUMA |
af705362a [PATCH] generify ... |
87 |
|
802f192e4 [PATCH] SPARSEMEM... |
88 |
# |
3e347261a [PATCH] sparsemem... |
89 |
# SPARSEMEM_EXTREME (which is the default) does some bootmem |
c89ab04fe mm/sparse: cleanu... |
90 |
# allocations when sparse_init() is called. If this cannot |
3e347261a [PATCH] sparsemem... |
91 92 93 94 95 96 97 98 |
# be done on your architecture, select this option. However, # statically allocating the mem_section[] array can potentially # consume vast quantities of .bss, so be careful. # # This option will also potentially produce smaller runtime code # with gcc 3.4 and later. # config SPARSEMEM_STATIC |
9ba16087d Kconfig: eliminat... |
99 |
bool |
3e347261a [PATCH] sparsemem... |
100 101 |
# |
44c09201a more misc typo fixes |
102 |
# Architecture platforms which require a two level mem_section in SPARSEMEM |
802f192e4 [PATCH] SPARSEMEM... |
103 104 105 |
# must select this option. This is usually for architecture platforms with # an extremely sparse physical address space. # |
3e347261a [PATCH] sparsemem... |
106 107 108 |
config SPARSEMEM_EXTREME def_bool y depends on SPARSEMEM && !SPARSEMEM_STATIC |
4c21e2f24 [PATCH] mm: split... |
109 |
|
29c71111d vmemmap: generify... |
110 |
config SPARSEMEM_VMEMMAP_ENABLE |
9ba16087d Kconfig: eliminat... |
111 |
bool |
29c71111d vmemmap: generify... |
112 113 |
config SPARSEMEM_VMEMMAP |
a5ee6daa5 sparsemem: make S... |
114 115 116 117 |
bool "Sparse Memory virtual memmap" depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE default y help |
19fa40a0f mm/Kconfig: fix i... |
118 119 120 |
SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise pfn_to_page and page_to_pfn operations. This is the most efficient option when sufficient kernel resources are available. |
29c71111d vmemmap: generify... |
121 |
|
70210ed95 mm/memblock: add ... |
122 |
config HAVE_MEMBLOCK_PHYS_MAP |
6341e62b2 kconfig: use bool... |
123 |
bool |
70210ed95 mm/memblock: add ... |
124 |
|
67a929e09 mm: rename CONFIG... |
125 |
config HAVE_FAST_GUP |
050a9adc6 mm: consolidate t... |
126 |
depends on MMU |
6341e62b2 kconfig: use bool... |
127 |
bool |
2667f50e8 mm: introduce a g... |
128 |
|
52219aeaf mm/memory_hotplug... |
129 130 131 |
# Don't discard allocated memory used to track "memory" and "reserved" memblocks # after early boot, so it can still be used to test for validity of memory. # Also, memblocks are updated with memory hot(un)plug. |
350e88bad mm: memblock: mak... |
132 |
config ARCH_KEEP_MEMBLOCK |
6341e62b2 kconfig: use bool... |
133 |
bool |
c378ddd53 memblock, x86: Ma... |
134 |
|
1e5d8e1e4 x86/mm: Introduce... |
135 136 137 |
# Keep arch NUMA mapping infrastructure post-init. config NUMA_KEEP_MEMINFO bool |
ee6f509c3 mm: factor out me... |
138 |
config MEMORY_ISOLATION |
6341e62b2 kconfig: use bool... |
139 |
bool |
ee6f509c3 mm: factor out me... |
140 |
|
46723bfa5 memory-hotplug: i... |
141 142 143 144 145 146 |
# # Only be set on architectures that have completely implemented memory hotplug # feature. If you are not sure, don't touch it. # config HAVE_BOOTMEM_INFO_NODE def_bool n |
3947be196 [PATCH] memory ho... |
147 148 149 |
# eventually, we can have this option just 'select SPARSEMEM' config MEMORY_HOTPLUG bool "Allow for memory hot-add" |
b30c59279 mm/memory_hotplug... |
150 |
select MEMORY_ISOLATION |
ec69acbb1 [PATCH] hot-add-m... |
151 |
depends on SPARSEMEM || X86_64_ACPI_NUMA |
40b313608 Finally eradicate... |
152 |
depends on ARCH_ENABLE_MEMORY_HOTPLUG |
b59d02ed0 mm/memory_hotplug... |
153 |
depends on 64BIT || BROKEN |
1e5d8e1e4 x86/mm: Introduce... |
154 |
select NUMA_KEEP_MEMINFO if NUMA |
3947be196 [PATCH] memory ho... |
155 |
|
ec69acbb1 [PATCH] hot-add-m... |
156 157 158 |
config MEMORY_HOTPLUG_SPARSE def_bool y depends on SPARSEMEM && MEMORY_HOTPLUG |
8604d9e53 memory_hotplug: i... |
159 |
config MEMORY_HOTPLUG_DEFAULT_ONLINE |
19fa40a0f mm/Kconfig: fix i... |
160 161 162 |
bool "Online the newly added memory blocks by default" depends on MEMORY_HOTPLUG help |
8604d9e53 memory_hotplug: i... |
163 164 165 166 |
This option sets the default policy setting for memory hotplug onlining policy (/sys/devices/system/memory/auto_online_blocks) which determines what happens to newly added memory regions. Policy setting can always be changed at runtime. |
cb1aaebea docs: fix broken ... |
167 |
See Documentation/admin-guide/mm/memory-hotplug.rst for more information. |
8604d9e53 memory_hotplug: i... |
168 169 170 171 172 |
Say Y here if you want all hot-plugged memory blocks to appear in 'online' state by default. Say N here if you want the default policy to keep all hot-plugged memory blocks in 'offline' state. |
0c0e61958 memory unplug: pa... |
173 174 |
config MEMORY_HOTREMOVE bool "Allow for memory hot remove" |
f7e3334a6 powerpc: Fix memo... |
175 |
select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64) |
0c0e61958 memory unplug: pa... |
176 177 |
depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE depends on MIGRATION |
4c21e2f24 [PATCH] mm: split... |
178 179 180 181 182 |
# Heavily threaded applications may benefit from splitting the mm-wide # page_table_lock, so that faults on different parts of the user address # space can be handled with less contention: split it at this NR_CPUS. # Default to 4 for wider testing, though 8 might be more appropriate. # ARM's adjust_pte (unused if VIPT) depends on mm-wide page_table_lock. |
7b6ac9dff [PATCH] mm: updat... |
183 |
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes. |
60bccaa67 sparc32: mm: Disa... |
184 185 186 |
# SPARC32 allocates multiple pte tables within a single page, and therefore # a per-page lock leads to problems when multiple tables need to be locked # at the same time (e.g. copy_page_range()). |
a70caa8ba mm: stop ptlock e... |
187 |
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page. |
4c21e2f24 [PATCH] mm: split... |
188 189 190 |
# config SPLIT_PTLOCK_CPUS int |
9164550ec mm: disable split... |
191 |
default "999999" if !MMU |
a70caa8ba mm: stop ptlock e... |
192 193 |
default "999999" if ARM && !CPU_CACHE_VIPT default "999999" if PARISC && !PA20 |
60bccaa67 sparc32: mm: Disa... |
194 |
default "999999" if SPARC32 |
4c21e2f24 [PATCH] mm: split... |
195 |
default "4" |
7cbe34cf8 [PATCH] Swap Migr... |
196 |
|
e009bb30c mm: implement spl... |
197 |
config ARCH_ENABLE_SPLIT_PMD_PTLOCK |
6341e62b2 kconfig: use bool... |
198 |
bool |
e009bb30c mm: implement spl... |
199 |
|
7cbe34cf8 [PATCH] Swap Migr... |
200 |
# |
09316c09d mm/balloon_compac... |
201 202 |
# support for memory balloon config MEMORY_BALLOON |
6341e62b2 kconfig: use bool... |
203 |
bool |
09316c09d mm/balloon_compac... |
204 205 |
# |
18468d93e mm: introduce a c... |
206 207 208 209 |
# support for memory balloon compaction config BALLOON_COMPACTION bool "Allow for balloon memory compaction/migration" def_bool y |
09316c09d mm/balloon_compac... |
210 |
depends on COMPACTION && MEMORY_BALLOON |
18468d93e mm: introduce a c... |
211 212 213 214 215 216 217 218 219 220 |
help Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. Allowing the compaction & migration for memory pages enlisted as being part of memory balloon devices avoids the scenario aforementioned and helps improving memory defragmentation. # |
e9e96b39f mm: allow CONFIG_... |
221 222 223 |
# support for memory compaction config COMPACTION bool "Allow for memory compaction" |
05106e6a5 mm: enable CONFIG... |
224 |
def_bool y |
e9e96b39f mm: allow CONFIG_... |
225 |
select MIGRATION |
33a938774 mm: compaction: d... |
226 |
depends on MMU |
e9e96b39f mm: allow CONFIG_... |
227 |
help |
19fa40a0f mm/Kconfig: fix i... |
228 229 230 231 232 233 234 235 |
Compaction is the only memory management component to form high order (larger physically contiguous) memory blocks reliably. The page allocator relies on compaction heavily and the lack of the feature can lead to unexpected OOM killer invocations for high order memory requests. You shouldn't disable this option unless there really is a strong reason for it and then we would be really interested to hear about that at linux-mm@kvack.org. |
e9e96b39f mm: allow CONFIG_... |
236 237 |
# |
36e66c554 mm: introduce Rep... |
238 239 240 241 242 243 244 245 246 247 248 |
# support for free page reporting config PAGE_REPORTING bool "Free page reporting" def_bool n help Free page reporting allows for the incremental acquisition of free pages from the buddy allocator for the purpose of reporting those pages to another entity, such as a hypervisor, so that the memory can be freed within the host for other uses. # |
7cbe34cf8 [PATCH] Swap Migr... |
249 250 251 |
# support for page migration # config MIGRATION |
b20a35035 [PATCH] page migr... |
252 |
bool "Page migration" |
6c5240ae7 [PATCH] Swapless ... |
253 |
def_bool y |
de32a8177 mm/Kconfig: add M... |
254 |
depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU |
b20a35035 [PATCH] page migr... |
255 256 |
help Allows the migration of the physical location of pages of processes |
e9e96b39f mm: allow CONFIG_... |
257 258 259 260 261 |
while the virtual addresses are not changed. This is useful in two situations. The first is on NUMA systems to put pages nearer to the processors accessing. The second is when allocating huge pages as migration can relocate pages to satisfy a huge page allocation instead of reclaiming. |
6550e07f4 [PATCH] 64bit Res... |
262 |
|
c177c81e0 hugetlb: restrict... |
263 |
config ARCH_ENABLE_HUGEPAGE_MIGRATION |
6341e62b2 kconfig: use bool... |
264 |
bool |
c177c81e0 hugetlb: restrict... |
265 |
|
9c670ea37 mm: thp: introduc... |
266 267 |
config ARCH_ENABLE_THP_MIGRATION bool |
8df995f6b mm: simplify MEMO... |
268 |
config CONTIG_ALLOC |
19fa40a0f mm/Kconfig: fix i... |
269 |
def_bool (MEMORY_ISOLATION && COMPACTION) || CMA |
8df995f6b mm: simplify MEMO... |
270 |
|
600715dcd generic: add phys... |
271 |
config PHYS_ADDR_T_64BIT |
d4a451d5f arch: remove the ... |
272 |
def_bool 64BIT |
600715dcd generic: add phys... |
273 |
|
2a7326b5b CONFIG_BOUNCE to ... |
274 |
config BOUNCE |
9ca24e2e1 mmKconfig: add an... |
275 276 |
bool "Enable bounce buffers" default y |
2a7326b5b CONFIG_BOUNCE to ... |
277 |
depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM) |
9ca24e2e1 mmKconfig: add an... |
278 279 280 281 282 |
help Enable bounce buffers for devices that cannot access the full range of memory available to the CPU. Enabled by default when ZONE_DMA or HIGHMEM is selected, but you may say n to override this. |
2a7326b5b CONFIG_BOUNCE to ... |
283 |
|
f057eac0d Introduce CONFIG_... |
284 |
config VIRT_TO_BUS |
4febd95a8 Select VIRT_TO_BU... |
285 286 287 288 289 |
bool help An architecture should select this if it implements the deprecated interface virt_to_bus(). All new architectures should probably not select this. |
cddb8a5c1 mmu-notifiers: core |
290 291 292 |
config MMU_NOTIFIER bool |
83fe27ea5 rcu: Make SRCU op... |
293 |
select SRCU |
99cb252f5 mm/mmu_notifier: ... |
294 |
select INTERVAL_TREE |
fc4d5c292 nommu: make the i... |
295 |
|
f8af4da3b ksm: the mm inter... |
296 297 298 |
config KSM bool "Enable KSM for page merging" depends on MMU |
59e1a2f4b ksm: replace jhas... |
299 |
select XXHASH |
f8af4da3b ksm: the mm inter... |
300 301 302 303 |
help Enable Kernel Samepage Merging: KSM periodically scans those areas of an application's address space that an app has advised may be mergeable. When it finds pages of identical content, it replaces |
d0f209f68 ksm: remove unswa... |
304 |
the many instances by a single page with that content, so |
f8af4da3b ksm: the mm inter... |
305 306 |
saving memory until one or another app needs to modify the content. Recommended for use with KVM, or with other duplicative applications. |
ad56b738c docs/vm: rename d... |
307 |
See Documentation/vm/ksm.rst for more information: KSM is inactive |
c73602ad3 ksm: more on defa... |
308 309 |
until a program has madvised that an area is MADV_MERGEABLE, and root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set). |
f8af4da3b ksm: the mm inter... |
310 |
|
e0a94c2a6 security: use mma... |
311 |
config DEFAULT_MMAP_MIN_ADDR |
19fa40a0f mm/Kconfig: fix i... |
312 |
int "Low address space to protect from user allocation" |
6e1415467 NOMMU: Optimise a... |
313 |
depends on MMU |
19fa40a0f mm/Kconfig: fix i... |
314 315 |
default 4096 help |
e0a94c2a6 security: use mma... |
316 317 318 319 320 321 322 |
This is the portion of low virtual memory which should be protected from userspace allocation. Keeping a user from writing to low pages can help reduce the impact of kernel NULL pointer bugs. For most ia64, ppc64 and x86 users with lots of address space a value of 65536 is reasonable and should cause no problems. On arm and other archs it should not be higher than 32768. |
788084aba Security/SELinux:... |
323 324 325 |
Programs which use vm86 functionality or have some need to map this low address space will need CAP_SYS_RAWIO or disable this protection by setting the value to 0. |
e0a94c2a6 security: use mma... |
326 327 328 |
This value can be changed after boot using the /proc/sys/vm/mmap_min_addr tunable. |
d949f36f1 x86: Fix hwpoison... |
329 330 |
config ARCH_SUPPORTS_MEMORY_FAILURE bool |
e0a94c2a6 security: use mma... |
331 |
|
6a46079cf HWPOISON: The hig... |
332 333 |
config MEMORY_FAILURE depends on MMU |
d949f36f1 x86: Fix hwpoison... |
334 |
depends on ARCH_SUPPORTS_MEMORY_FAILURE |
6a46079cf HWPOISON: The hig... |
335 |
bool "Enable recovery from hardware memory errors" |
ee6f509c3 mm: factor out me... |
336 |
select MEMORY_ISOLATION |
97f0b1345 tracing: add trac... |
337 |
select RAS |
6a46079cf HWPOISON: The hig... |
338 339 340 341 342 |
help Enables code to recover from some memory failures on systems with MCA recovery. This allows a system to continue running even when some of its memory has uncorrected errors. This requires special hardware support and typically ECC memory. |
cae681fc1 HWPOISON: Add sim... |
343 |
config HWPOISON_INJECT |
413f9efbc HWPOISON: mention... |
344 |
tristate "HWPoison pages injector" |
27df5068e HWPOISON: Add PRO... |
345 |
depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS |
478c5ffc0 HWPOISON: add pag... |
346 |
select PROC_PAGE_MONITOR |
cae681fc1 HWPOISON: Add sim... |
347 |
|
fc4d5c292 nommu: make the i... |
348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 |
config NOMMU_INITIAL_TRIM_EXCESS int "Turn on mmap() excess space trimming before booting" depends on !MMU default 1 help The NOMMU mmap() frequently needs to allocate large contiguous chunks of memory on which to store mappings, but it can only ask the system allocator for chunks in 2^N*PAGE_SIZE amounts - which is frequently more than it requires. To deal with this, mmap() is able to trim off the excess and return it to the allocator. If trimming is enabled, the excess is trimmed off and returned to the system allocator, which can cause extra fragmentation, particularly if there are a lot of transient processes. If trimming is disabled, the excess is kept, but not used, which for long-term mappings means that the space is wasted. Trimming can be dynamically controlled through a sysctl option (/proc/sys/vm/nr_trim_pages) which specifies the minimum number of excess pages there must be before trimming should occur, or zero if no trimming is to occur. This option specifies the initial value of this option. The default of 1 says that all excess pages should be trimmed. |
dd19d2938 Fix references to... |
373 |
See Documentation/admin-guide/mm/nommu-mmap.rst for more information. |
bbddff054 percpu: use percp... |
374 |
|
4c76d9d1f thp: CONFIG_TRANS... |
375 |
config TRANSPARENT_HUGEPAGE |
13ece886d thp: transparent ... |
376 |
bool "Transparent Hugepage Support" |
15626062f thp, x86: introdu... |
377 |
depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE |
5d6892407 thp: select CONFI... |
378 |
select COMPACTION |
3a08cd52c radix tree: Remov... |
379 |
select XARRAY_MULTI |
4c76d9d1f thp: CONFIG_TRANS... |
380 381 382 383 384 385 386 387 388 |
help Transparent Hugepages allows the kernel to use huge pages and huge tlb transparently to the applications whenever possible. This feature can improve computing performance to certain applications by speeding up page faults during memory allocation, by reducing the number of tlb misses and by speeding up the pagetable walking. If memory constrained on embedded, you may want to say N. |
13ece886d thp: transparent ... |
389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 |
choice prompt "Transparent Hugepage Support sysfs defaults" depends on TRANSPARENT_HUGEPAGE default TRANSPARENT_HUGEPAGE_ALWAYS help Selects the sysfs defaults for Transparent Hugepage Support. config TRANSPARENT_HUGEPAGE_ALWAYS bool "always" help Enabling Transparent Hugepage always, can increase the memory footprint of applications without a guaranteed benefit but it will work automatically for all applications. config TRANSPARENT_HUGEPAGE_MADVISE bool "madvise" help Enabling Transparent Hugepage madvise, will only provide a performance improvement benefit to the applications using madvise(MADV_HUGEPAGE) but it won't risk to increase the memory footprint of applications without a guaranteed benefit. endchoice |
38d8b4e6b mm, THP, swap: de... |
412 |
config ARCH_WANTS_THP_SWAP |
19fa40a0f mm/Kconfig: fix i... |
413 |
def_bool n |
38d8b4e6b mm, THP, swap: de... |
414 415 416 |
config THP_SWAP def_bool y |
14fef2841 mm, swap: make CO... |
417 |
depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP |
38d8b4e6b mm, THP, swap: de... |
418 419 |
help Swap transparent huge pages in one piece, without splitting. |
14fef2841 mm, swap: make CO... |
420 421 |
XXX: For now, swap cluster backing transparent huge page will be split after swapout. |
38d8b4e6b mm, THP, swap: de... |
422 423 |
For selection by architectures with reasonable THP sizes. |
e496cf3d7 thp: introduce CO... |
424 |
# |
bbddff054 percpu: use percp... |
425 426 427 428 429 430 |
# UP and nommu archs use km based percpu allocator # config NEED_PER_CPU_KM depends on !SMP bool default y |
077b1f83a mm: cleancache co... |
431 432 433 |
config CLEANCACHE bool "Enable cleancache driver to cache clean pages if tmem is present" |
077b1f83a mm: cleancache co... |
434 435 436 437 438 |
help Cleancache can be thought of as a page-granularity victim cache for clean pages that the kernel's pageframe replacement algorithm (PFRA) would like to keep around, but can't since there isn't enough memory. So when the PFRA "evicts" a page, it first attempts to use |
140a1ef2f mm Kconfig typo: ... |
439 |
cleancache code to put the data contained in that page into |
077b1f83a mm: cleancache co... |
440 441 442 443 444 445 446 447 448 449 450 451 452 |
"transcendent memory", memory that is not directly accessible or addressable by the kernel and is of unknown and possibly time-varying size. And when a cleancache-enabled filesystem wishes to access a page in a file on disk, it first checks cleancache to see if it already contains it; if it does, the page is copied into the kernel and a disk access is avoided. When a transcendent memory driver is available (such as zcache or Xen transcendent memory), a significant I/O reduction may be achieved. When none is available, all cleancache calls are reduced to a single pointer-compare-against-NULL resulting in a negligible performance hit. If unsure, say Y to enable cleancache |
27c6aec21 mm: frontswap: co... |
453 454 455 456 |
config FRONTSWAP bool "Enable frontswap to cache swap pages if tmem is present" depends on SWAP |
27c6aec21 mm: frontswap: co... |
457 458 459 460 461 462 463 464 465 466 467 468 |
help Frontswap is so named because it can be thought of as the opposite of a "backing" store for a swap device. The data is stored into "transcendent memory", memory that is not directly accessible or addressable by the kernel and is of unknown and possibly time-varying size. When space in transcendent memory is available, a significant swap I/O reduction may be achieved. When none is available, all frontswap calls are reduced to a single pointer- compare-against-NULL resulting in a negligible performance hit and swap data is stored as normal on the matching swap device. If unsure, say Y to enable frontswap. |
f825c736e mm/cma: Move dma ... |
469 470 471 |
config CMA bool "Contiguous Memory Allocator" |
aca52c398 mm: remove CONFIG... |
472 |
depends on MMU |
f825c736e mm/cma: Move dma ... |
473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 |
select MIGRATION select MEMORY_ISOLATION help This enables the Contiguous Memory Allocator which allows other subsystems to allocate big physically-contiguous blocks of memory. CMA reserves a region of memory and allows only movable pages to be allocated from it. This way, the kernel can use the memory for pagecache and when a subsystem requests for contiguous area, the allocated pages are migrated away to serve the contiguous request. If unsure, say "n". config CMA_DEBUG bool "CMA debug messages (DEVELOPMENT)" depends on DEBUG_KERNEL && CMA help Turns on debug messages in CMA. This produces KERN_DEBUG messages for every CMA call as well as various messages while processing calls such as dma_alloc_from_contiguous(). This option does not affect warning and error messages. |
bf550fc93 Merge remote-trac... |
493 |
|
28b24c1fc mm: cma: debugfs ... |
494 495 496 497 498 |
config CMA_DEBUGFS bool "CMA debugfs interface" depends on CMA && DEBUG_FS help Turns on the DebugFS interface for CMA. |
a254129e8 CMA: generalize C... |
499 500 501 |
config CMA_AREAS int "Maximum count of the CMA areas" depends on CMA |
b7176c261 dma-contiguous: p... |
502 |
default 19 if NUMA |
a254129e8 CMA: generalize C... |
503 504 505 506 507 |
default 7 help CMA allows to create CMA areas for particular purpose, mainly, used as device private area. This parameter sets the maximum number of CMA area in the system. |
b7176c261 dma-contiguous: p... |
508 |
If unsure, leave the default value "7" in UMA and "19" in NUMA. |
a254129e8 CMA: generalize C... |
509 |
|
af8d417a0 mm/zpool: impleme... |
510 511 512 513 |
config MEM_SOFT_DIRTY bool "Track memory changes" depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS select PROC_PAGE_MONITOR |
4e2e2770b zbud: add to mm/ |
514 |
help |
af8d417a0 mm/zpool: impleme... |
515 516 517 518 |
This option enables memory changes tracking by introducing a soft-dirty bit on pte-s. This bit it set when someone writes into a page just as regular dirty bit, but unlike the latter it can be cleared by hands. |
1ad1335dc docs/admin-guide/... |
519 |
See Documentation/admin-guide/mm/soft-dirty.rst for more details. |
4e2e2770b zbud: add to mm/ |
520 |
|
2b2811178 zswap: add to mm/ |
521 522 523 |
config ZSWAP bool "Compressed cache for swap pages (EXPERIMENTAL)" depends on FRONTSWAP && CRYPTO=y |
12d79d64b mm/zpool: update ... |
524 |
select ZPOOL |
2b2811178 zswap: add to mm/ |
525 526 527 528 529 530 531 532 533 534 535 536 537 |
help A lightweight compressed cache for swap pages. It takes pages that are in the process of being swapped out and attempts to compress them into a dynamically allocated RAM-based memory pool. This can result in a significant I/O reduction on swap device and, in the case where decompressing from RAM is faster that swap device reads, can also improve workload performance. This is marked experimental because it is a new feature (as of v3.11) that interacts heavily with memory reclaim. While these interactions don't cause any known issues on simple memory setups, they have not be fully explored on the large set of potential configurations and workloads that exist. |
bb8b93b5b mm/zswap: allow s... |
538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 |
choice prompt "Compressed cache for swap pages default compressor" depends on ZSWAP default ZSWAP_COMPRESSOR_DEFAULT_LZO help Selects the default compression algorithm for the compressed cache for swap pages. For an overview what kind of performance can be expected from a particular compression algorithm please refer to the benchmarks available at the following LWN page: https://lwn.net/Articles/751795/ If in doubt, select 'LZO'. The selection made here can be overridden by using the kernel command line 'zswap.compressor=' option. config ZSWAP_COMPRESSOR_DEFAULT_DEFLATE bool "Deflate" select CRYPTO_DEFLATE help Use the Deflate algorithm as the default compression algorithm. config ZSWAP_COMPRESSOR_DEFAULT_LZO bool "LZO" select CRYPTO_LZO help Use the LZO algorithm as the default compression algorithm. config ZSWAP_COMPRESSOR_DEFAULT_842 bool "842" select CRYPTO_842 help Use the 842 algorithm as the default compression algorithm. config ZSWAP_COMPRESSOR_DEFAULT_LZ4 bool "LZ4" select CRYPTO_LZ4 help Use the LZ4 algorithm as the default compression algorithm. config ZSWAP_COMPRESSOR_DEFAULT_LZ4HC bool "LZ4HC" select CRYPTO_LZ4HC help Use the LZ4HC algorithm as the default compression algorithm. config ZSWAP_COMPRESSOR_DEFAULT_ZSTD bool "zstd" select CRYPTO_ZSTD help Use the zstd algorithm as the default compression algorithm. endchoice config ZSWAP_COMPRESSOR_DEFAULT string depends on ZSWAP default "deflate" if ZSWAP_COMPRESSOR_DEFAULT_DEFLATE default "lzo" if ZSWAP_COMPRESSOR_DEFAULT_LZO default "842" if ZSWAP_COMPRESSOR_DEFAULT_842 default "lz4" if ZSWAP_COMPRESSOR_DEFAULT_LZ4 default "lz4hc" if ZSWAP_COMPRESSOR_DEFAULT_LZ4HC default "zstd" if ZSWAP_COMPRESSOR_DEFAULT_ZSTD default "" choice prompt "Compressed cache for swap pages default allocator" depends on ZSWAP default ZSWAP_ZPOOL_DEFAULT_ZBUD help Selects the default allocator for the compressed cache for swap pages. The default is 'zbud' for compatibility, however please do read the description of each of the allocators below before making a right choice. The selection made here can be overridden by using the kernel command line 'zswap.zpool=' option. config ZSWAP_ZPOOL_DEFAULT_ZBUD bool "zbud" select ZBUD help Use the zbud allocator as the default allocator. config ZSWAP_ZPOOL_DEFAULT_Z3FOLD bool "z3fold" select Z3FOLD help Use the z3fold allocator as the default allocator. config ZSWAP_ZPOOL_DEFAULT_ZSMALLOC bool "zsmalloc" select ZSMALLOC help Use the zsmalloc allocator as the default allocator. endchoice config ZSWAP_ZPOOL_DEFAULT string depends on ZSWAP default "zbud" if ZSWAP_ZPOOL_DEFAULT_ZBUD default "z3fold" if ZSWAP_ZPOOL_DEFAULT_Z3FOLD default "zsmalloc" if ZSWAP_ZPOOL_DEFAULT_ZSMALLOC default "" config ZSWAP_DEFAULT_ON bool "Enable the compressed cache for swap pages by default" depends on ZSWAP help If selected, the compressed cache for swap pages will be enabled at boot, otherwise it will be disabled. The selection made here can be overridden by using the kernel command line 'zswap.enabled=' option. |
af8d417a0 mm/zpool: impleme... |
654 655 |
config ZPOOL tristate "Common API for compressed memory storage" |
0f8975ec4 mm: soft-dirty bi... |
656 |
help |
af8d417a0 mm/zpool: impleme... |
657 658 |
Compressed memory storage API. This allows using either zbud or zsmalloc. |
0f8975ec4 mm: soft-dirty bi... |
659 |
|
af8d417a0 mm/zpool: impleme... |
660 |
config ZBUD |
9a001fc19 z3fold: the 3-fol... |
661 |
tristate "Low (Up to 2x) density storage for compressed pages" |
af8d417a0 mm/zpool: impleme... |
662 663 664 665 666 667 |
help A special purpose allocator for storing compressed pages. It is designed to store up to two compressed pages per physical page. While this design limits storage density, it has simple and deterministic reclaim properties that make it preferable to a higher density approach when reclaim will be used. |
bcf1647d0 zsmalloc: move it... |
668 |
|
9a001fc19 z3fold: the 3-fol... |
669 670 671 |
config Z3FOLD tristate "Up to 3x density storage for compressed pages" depends on ZPOOL |
9a001fc19 z3fold: the 3-fol... |
672 673 674 675 676 |
help A special purpose allocator for storing compressed pages. It is designed to store up to three compressed pages per physical page. It is a ZBUD derivative so the simplicity and determinism are still there. |
bcf1647d0 zsmalloc: move it... |
677 |
config ZSMALLOC |
d867f203b mm/zsmalloc: make... |
678 |
tristate "Memory allocator for compressed pages" |
bcf1647d0 zsmalloc: move it... |
679 |
depends on MMU |
bcf1647d0 zsmalloc: move it... |
680 681 682 683 684 685 686 |
help zsmalloc is a slab-based memory allocator designed to store compressed RAM pages. zsmalloc uses virtual memory mapping in order to reduce fragmentation. However, this results in a non-standard allocator interface where a handle, not a pointer, is returned by an alloc(). This handle must be mapped in order to access the allocated space. |
0f050d997 mm/zsmalloc: add ... |
687 688 689 690 691 692 693 694 695 |
config ZSMALLOC_STAT bool "Export zsmalloc statistics" depends on ZSMALLOC select DEBUG_FS help This option enables code in the zsmalloc to collect various statistics about whats happening in zsmalloc and exports that information to userspace via debugfs. If unsure, say N. |
9e5c33d7a mm: create generi... |
696 697 |
config GENERIC_EARLY_IOREMAP bool |
042d27acb parisc,metag: Do ... |
698 699 700 701 |
config MAX_STACK_SIZE_MB int "Maximum user stack size for 32-bit processes (MB)" default 80 |
042d27acb parisc,metag: Do ... |
702 703 704 705 706 |
range 8 2048 depends on STACK_GROWSUP && (!64BIT || COMPAT) help This is the maximum stack size in Megabytes in the VM layout of 32-bit user processes when the stack grows upwards (currently only on parisc |
5f171577b Drop a bunch of m... |
707 708 709 |
arch). The stack will be located at the highest memory address minus the given value, unless the RLIMIT_STACK hard limit is changed to a smaller value in which case that is used. |
042d27acb parisc,metag: Do ... |
710 711 |
A sane initial value is 80 MB. |
3a80a7fa7 mm: meminit: init... |
712 |
|
3a80a7fa7 mm: meminit: init... |
713 |
config DEFERRED_STRUCT_PAGE_INIT |
1ce221036 mm/Kconfig: corre... |
714 |
bool "Defer initialisation of struct pages to kthreads" |
d39f8fb4b mm: make DEFERRED... |
715 |
depends on SPARSEMEM |
ab1e8d896 mm: don't allow d... |
716 |
depends on !NEED_PER_CPU_KM |
889c695d4 mm: disable defer... |
717 |
depends on 64BIT |
e44431498 mm: parallelize d... |
718 |
select PADATA |
3a80a7fa7 mm: meminit: init... |
719 720 721 722 |
help Ordinarily all struct pages are initialised during early boot in a single thread. On very large machines this can take a considerable amount of time. If this option is set, large machines will bring up |
e44431498 mm: parallelize d... |
723 724 |
a subset of memmap at boot and then initialise the rest in parallel. This has a potential performance impact on tasks running early in the |
1ce221036 mm/Kconfig: corre... |
725 726 |
lifetime of the system until these kthreads finish the initialisation. |
033fbae98 mm: ZONE_DEVICE f... |
727 |
|
33c3fc71c mm: introduce idl... |
728 729 730 731 732 733 734 735 736 |
config IDLE_PAGE_TRACKING bool "Enable idle page tracking" depends on SYSFS && MMU select PAGE_EXTENSION if !64BIT help This feature allows to estimate the amount of user pages that have not been touched during a given period of time. This information can be useful to tune memory cgroup limits and/or for job placement within a compute cluster. |
1ad1335dc docs/admin-guide/... |
737 738 |
See Documentation/admin-guide/mm/idle_page_tracking.rst for more details. |
33c3fc71c mm: introduce idl... |
739 |
|
175967318 mm: introduce ARC... |
740 |
config ARCH_HAS_PTE_DEVMAP |
65f7d0497 mm, x86: Add ARCH... |
741 |
bool |
033fbae98 mm: ZONE_DEVICE f... |
742 |
config ZONE_DEVICE |
5042db43c mm/ZONE_DEVICE: n... |
743 |
bool "Device memory (pmem, HMM, etc...) hotplug support" |
033fbae98 mm: ZONE_DEVICE f... |
744 745 |
depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE |
99490f16f mm: ZONE_DEVICE d... |
746 |
depends on SPARSEMEM_VMEMMAP |
175967318 mm: introduce ARC... |
747 |
depends on ARCH_HAS_PTE_DEVMAP |
3a08cd52c radix tree: Remov... |
748 |
select XARRAY_MULTI |
033fbae98 mm: ZONE_DEVICE f... |
749 750 751 752 753 754 755 756 757 |
help Device memory hotplug support allows for establishing pmem, or other device driver discovered memory regions, in the memmap. This allows pfn_to_page() lookups of otherwise "device-physical" addresses which is needed for using a DAX mapping in an O_DIRECT operation, among other things. If FS_DAX is enabled, then say Y. |
06a660ada Merge tag 'media/... |
758 |
|
e76384884 mm: introduce MEM... |
759 760 |
config DEV_PAGEMAP_OPS bool |
9c240a7bb mm/hmm: make HMM_... |
761 762 763 764 |
# # Helpers to mirror range of the CPU page tables of a process into device page # tables. # |
c0b124054 mm/hmm/mirror: mi... |
765 |
config HMM_MIRROR |
9c240a7bb mm/hmm: make HMM_... |
766 |
bool |
f442c283e mm/hmm: allow HMM... |
767 |
depends on MMU |
c0b124054 mm/hmm/mirror: mi... |
768 |
|
5042db43c mm/ZONE_DEVICE: n... |
769 770 |
config DEVICE_PRIVATE bool "Unaddressable device memory (GPU memory, ...)" |
7328d9cc1 mm: sort out the ... |
771 |
depends on ZONE_DEVICE |
e76384884 mm: introduce MEM... |
772 |
select DEV_PAGEMAP_OPS |
5042db43c mm/ZONE_DEVICE: n... |
773 774 775 776 777 |
help Allows creation of struct pages to represent unaddressable device memory; i.e., memory that is only accessible from the device (or group of devices). You likely also want to select HMM_MIRROR. |
3e9a9e256 mm: add a vmap_pf... |
778 779 |
config VMAP_PFN bool |
8025e5ddf [media] mm: Provi... |
780 781 |
config FRAME_VECTOR bool |
63c17fb8e mm/core, x86/mm/p... |
782 783 784 |
config ARCH_USES_HIGH_VMA_FLAGS bool |
66d375709 mm/core, x86/mm/p... |
785 786 |
config ARCH_HAS_PKEYS bool |
30a5b5367 percpu: expose st... |
787 788 789 |
config PERCPU_STATS bool "Collect percpu memory statistics" |
30a5b5367 percpu: expose st... |
790 791 792 793 |
help This feature collects and exposes statistics via debugfs. The information includes global and per chunk statistics, which can be used to help understand percpu memory usage. |
64c349f4a mm: add infrastru... |
794 795 |
config GUP_BENCHMARK |
4c6cd03ed mm/gup_benchmark:... |
796 |
bool "Enable infrastructure for get_user_pages() and related calls benchmarking" |
64c349f4a mm: add infrastru... |
797 798 |
help Provides /sys/kernel/debug/gup_benchmark that helps with testing |
4c6cd03ed mm/gup_benchmark:... |
799 |
performance of get_user_pages() and related calls. |
64c349f4a mm: add infrastru... |
800 801 |
See tools/testing/selftests/vm/gup_benchmark.c |
3010a5ea6 mm: introduce ARC... |
802 |
|
39656e83d mm: lift the x86_... |
803 804 |
config GUP_GET_PTE_LOW_HIGH bool |
99cb0dbd4 mm,thp: add read-... |
805 806 |
config READ_ONLY_THP_FOR_FS bool "Read-only THP for filesystems (EXPERIMENTAL)" |
396bcc529 mm: remove CONFIG... |
807 |
depends on TRANSPARENT_HUGEPAGE && SHMEM |
99cb0dbd4 mm,thp: add read-... |
808 809 810 811 812 813 814 |
help Allow khugepaged to put read-only file-backed pages in THP. This is marked experimental because it is a new feature. Write support of file THPs will be developed in the next few release cycles. |
3010a5ea6 mm: introduce ARC... |
815 816 |
config ARCH_HAS_PTE_SPECIAL bool |
59e0b520c kconfig: add a Me... |
817 |
|
cbd34da7d mm: move the powe... |
818 819 820 821 822 823 824 825 826 |
# # Some architectures require a special hugepage directory format that is # required to support multiple hugepage sizes. For example a4fe3ce76 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables" # introduced it on powerpc. This allows for a more flexible hugepage # pagetable layouts. # config ARCH_HAS_HUGEPD bool |
c5acad84c mm: Add write-pro... |
827 828 |
config MAPPING_DIRTY_HELPERS bool |
59e0b520c kconfig: add a Me... |
829 |
endmenu |