]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - mm/Kconfig
Merge remote-tracking branches 'asoc/topic/inntel', 'asoc/topic/input', 'asoc/topic...
[mirror_ubuntu-bionic-kernel.git] / mm / Kconfig
CommitLineData
e1785e85
DH
1config SELECT_MEMORY_MODEL
2 def_bool y
a8826eeb 3 depends on ARCH_SELECT_MEMORY_MODEL
e1785e85 4
3a9da765
DH
5choice
6 prompt "Memory model"
e1785e85
DH
7 depends on SELECT_MEMORY_MODEL
8 default DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT
d41dee36 9 default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT
e1785e85 10 default FLATMEM_MANUAL
3a9da765 11
e1785e85 12config FLATMEM_MANUAL
3a9da765 13 bool "Flat Memory"
c898ec16 14 depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE
3a9da765
DH
15 help
16 This option allows you to change some of the ways that
17 Linux manages its memory internally. Most users will
18 only have one option here: FLATMEM. This is normal
19 and a correct option.
20
d41dee36
AW
21 Some users of more advanced features like NUMA and
22 memory hotplug may have different options here.
18f65332 23 DISCONTIGMEM is a more mature, better tested system,
d41dee36
AW
24 but is incompatible with memory hotplug and may suffer
25 decreased performance over SPARSEMEM. If unsure between
26 "Sparse Memory" and "Discontiguous Memory", choose
27 "Discontiguous Memory".
28
29 If unsure, choose this option (Flat Memory) over any other.
3a9da765 30
e1785e85 31config DISCONTIGMEM_MANUAL
f3519f91 32 bool "Discontiguous Memory"
3a9da765
DH
33 depends on ARCH_DISCONTIGMEM_ENABLE
34 help
785dcd44
DH
35 This option provides enhanced support for discontiguous
36 memory systems, over FLATMEM. These systems have holes
37 in their physical address spaces, and this option provides
38 more efficient handling of these holes. However, the vast
39 majority of hardware has quite flat address spaces, and
ad3d0a38 40 can have degraded performance from the extra overhead that
785dcd44
DH
41 this option imposes.
42
43 Many NUMA configurations will have this as the only option.
44
3a9da765
DH
45 If unsure, choose "Flat Memory" over this option.
46
d41dee36
AW
47config SPARSEMEM_MANUAL
48 bool "Sparse Memory"
49 depends on ARCH_SPARSEMEM_ENABLE
50 help
51 This will be the only option for some systems, including
52 memory hotplug systems. This is normal.
53
54 For many other systems, this will be an alternative to
f3519f91 55 "Discontiguous Memory". This option provides some potential
d41dee36
AW
56 performance benefits, along with decreased code complexity,
57 but it is newer, and more experimental.
58
59 If unsure, choose "Discontiguous Memory" or "Flat Memory"
60 over this option.
61
3a9da765
DH
62endchoice
63
e1785e85
DH
64config DISCONTIGMEM
65 def_bool y
66 depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL
67
d41dee36
AW
68config SPARSEMEM
69 def_bool y
1a83e175 70 depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL
d41dee36 71
e1785e85
DH
72config FLATMEM
73 def_bool y
d41dee36
AW
74 depends on (!DISCONTIGMEM && !SPARSEMEM) || FLATMEM_MANUAL
75
76config FLAT_NODE_MEM_MAP
77 def_bool y
78 depends on !SPARSEMEM
e1785e85 79
93b7504e
DH
80#
81# Both the NUMA code and DISCONTIGMEM use arrays of pg_data_t's
82# to represent different areas of memory. This variable allows
83# those dependencies to exist individually.
84#
85config NEED_MULTIPLE_NODES
86 def_bool y
87 depends on DISCONTIGMEM || NUMA
af705362
AW
88
89config HAVE_MEMORY_PRESENT
90 def_bool y
d41dee36 91 depends on ARCH_HAVE_MEMORY_PRESENT || SPARSEMEM
802f192e 92
3e347261
BP
93#
94# SPARSEMEM_EXTREME (which is the default) does some bootmem
84eb8d06 95# allocations when memory_present() is called. If this cannot
3e347261
BP
96# be done on your architecture, select this option. However,
97# statically allocating the mem_section[] array can potentially
98# consume vast quantities of .bss, so be careful.
99#
100# This option will also potentially produce smaller runtime code
101# with gcc 3.4 and later.
102#
103config SPARSEMEM_STATIC
9ba16087 104 bool
3e347261 105
802f192e 106#
44c09201 107# Architecture platforms which require a two level mem_section in SPARSEMEM
802f192e
BP
108# must select this option. This is usually for architecture platforms with
109# an extremely sparse physical address space.
110#
3e347261
BP
111config SPARSEMEM_EXTREME
112 def_bool y
113 depends on SPARSEMEM && !SPARSEMEM_STATIC
4c21e2f2 114
29c71111 115config SPARSEMEM_VMEMMAP_ENABLE
9ba16087 116 bool
29c71111 117
9bdac914
YL
118config SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
119 def_bool y
120 depends on SPARSEMEM && X86_64
121
29c71111 122config SPARSEMEM_VMEMMAP
a5ee6daa
GL
123 bool "Sparse Memory virtual memmap"
124 depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE
125 default y
126 help
127 SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise
128 pfn_to_page and page_to_pfn operations. This is the most
129 efficient option when sufficient kernel resources are available.
29c71111 130
95f72d1e 131config HAVE_MEMBLOCK
6341e62b 132 bool
95f72d1e 133
7c0caeb8 134config HAVE_MEMBLOCK_NODE_MAP
6341e62b 135 bool
7c0caeb8 136
70210ed9 137config HAVE_MEMBLOCK_PHYS_MAP
6341e62b 138 bool
70210ed9 139
2667f50e 140config HAVE_GENERIC_RCU_GUP
6341e62b 141 bool
2667f50e 142
c378ddd5 143config ARCH_DISCARD_MEMBLOCK
6341e62b 144 bool
c378ddd5 145
66616720 146config NO_BOOTMEM
6341e62b 147 bool
66616720 148
ee6f509c 149config MEMORY_ISOLATION
6341e62b 150 bool
ee6f509c 151
20b2f52b 152config MOVABLE_NODE
6341e62b 153 bool "Enable to assign a node which has only movable memory"
20b2f52b
LJ
154 depends on HAVE_MEMBLOCK
155 depends on NO_BOOTMEM
156 depends on X86_64
157 depends on NUMA
c2974058
TC
158 default n
159 help
160 Allow a node to have only movable memory. Pages used by the kernel,
161 such as direct mapping pages cannot be migrated. So the corresponding
c5320926
TC
162 memory device cannot be hotplugged. This option allows the following
163 two things:
164 - When the system is booting, node full of hotpluggable memory can
165 be arranged to have only movable memory so that the whole node can
166 be hot-removed. (need movable_node boot option specified).
167 - After the system is up, the option allows users to online all the
168 memory of a node as movable memory so that the whole node can be
169 hot-removed.
170
171 Users who don't use the memory hotplug feature are fine with this
172 option on since they don't specify movable_node boot option or they
173 don't online memory as movable.
c2974058
TC
174
175 Say Y here if you want to hotplug a whole node.
176 Say N here if you want kernel to use memory on all nodes evenly.
20b2f52b 177
46723bfa
YI
178#
179# Only be set on architectures that have completely implemented memory hotplug
180# feature. If you are not sure, don't touch it.
181#
182config HAVE_BOOTMEM_INFO_NODE
183 def_bool n
184
3947be19
DH
185# eventually, we can have this option just 'select SPARSEMEM'
186config MEMORY_HOTPLUG
187 bool "Allow for memory hot-add"
ec69acbb 188 depends on SPARSEMEM || X86_64_ACPI_NUMA
40b31360 189 depends on ARCH_ENABLE_MEMORY_HOTPLUG
67463e54 190 depends on COMPILE_TEST || !KASAN
3947be19 191
ec69acbb
KM
192config MEMORY_HOTPLUG_SPARSE
193 def_bool y
194 depends on SPARSEMEM && MEMORY_HOTPLUG
195
8604d9e5
VK
196config MEMORY_HOTPLUG_DEFAULT_ONLINE
197 bool "Online the newly added memory blocks by default"
198 default n
199 depends on MEMORY_HOTPLUG
200 help
201 This option sets the default policy setting for memory hotplug
202 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
203 determines what happens to newly added memory regions. Policy setting
204 can always be changed at runtime.
205 See Documentation/memory-hotplug.txt for more information.
206
207 Say Y here if you want all hot-plugged memory blocks to appear in
208 'online' state by default.
209 Say N here if you want the default policy to keep all hot-plugged
210 memory blocks in 'offline' state.
211
0c0e6195
KH
212config MEMORY_HOTREMOVE
213 bool "Allow for memory hot remove"
46723bfa 214 select MEMORY_ISOLATION
f7e3334a 215 select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64)
0c0e6195
KH
216 depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
217 depends on MIGRATION
218
4c21e2f2
HD
219# Heavily threaded applications may benefit from splitting the mm-wide
220# page_table_lock, so that faults on different parts of the user address
221# space can be handled with less contention: split it at this NR_CPUS.
222# Default to 4 for wider testing, though 8 might be more appropriate.
223# ARM's adjust_pte (unused if VIPT) depends on mm-wide page_table_lock.
7b6ac9df 224# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
a70caa8b 225# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
4c21e2f2
HD
226#
227config SPLIT_PTLOCK_CPUS
228 int
9164550e 229 default "999999" if !MMU
a70caa8b
HD
230 default "999999" if ARM && !CPU_CACHE_VIPT
231 default "999999" if PARISC && !PA20
4c21e2f2 232 default "4"
7cbe34cf 233
e009bb30 234config ARCH_ENABLE_SPLIT_PMD_PTLOCK
6341e62b 235 bool
e009bb30 236
09316c09
KK
237#
238# support for memory balloon
239config MEMORY_BALLOON
6341e62b 240 bool
09316c09 241
18468d93
RA
242#
243# support for memory balloon compaction
244config BALLOON_COMPACTION
245 bool "Allow for balloon memory compaction/migration"
246 def_bool y
09316c09 247 depends on COMPACTION && MEMORY_BALLOON
18468d93
RA
248 help
249 Memory fragmentation introduced by ballooning might reduce
250 significantly the number of 2MB contiguous memory blocks that can be
251 used within a guest, thus imposing performance penalties associated
252 with the reduced number of transparent huge pages that could be used
253 by the guest workload. Allowing the compaction & migration for memory
254 pages enlisted as being part of memory balloon devices avoids the
255 scenario aforementioned and helps improving memory defragmentation.
256
e9e96b39
MG
257#
258# support for memory compaction
259config COMPACTION
260 bool "Allow for memory compaction"
05106e6a 261 def_bool y
e9e96b39 262 select MIGRATION
33a93877 263 depends on MMU
e9e96b39 264 help
b32eaf71
MH
265 Compaction is the only memory management component to form
266 high order (larger physically contiguous) memory blocks
267 reliably. The page allocator relies on compaction heavily and
268 the lack of the feature can lead to unexpected OOM killer
269 invocations for high order memory requests. You shouldn't
270 disable this option unless there really is a strong reason for
271 it and then we would be really interested to hear about that at
272 linux-mm@kvack.org.
e9e96b39 273
7cbe34cf
CL
274#
275# support for page migration
276#
277config MIGRATION
b20a3503 278 bool "Page migration"
6c5240ae 279 def_bool y
de32a817 280 depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU
b20a3503
CL
281 help
282 Allows the migration of the physical location of pages of processes
e9e96b39
MG
283 while the virtual addresses are not changed. This is useful in
284 two situations. The first is on NUMA systems to put pages nearer
285 to the processors accessing. The second is when allocating huge
286 pages as migration can relocate pages to satisfy a huge page
287 allocation instead of reclaiming.
6550e07f 288
c177c81e 289config ARCH_ENABLE_HUGEPAGE_MIGRATION
6341e62b 290 bool
c177c81e 291
600715dc
JF
292config PHYS_ADDR_T_64BIT
293 def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT
294
2a7326b5 295config BOUNCE
9ca24e2e
VM
296 bool "Enable bounce buffers"
297 default y
2a7326b5 298 depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)
9ca24e2e
VM
299 help
300 Enable bounce buffers for devices that cannot access
301 the full range of memory available to the CPU. Enabled
302 by default when ZONE_DMA or HIGHMEM is selected, but you
303 may say n to override this.
2a7326b5 304
ffecfd1a
DW
305# On the 'tile' arch, USB OHCI needs the bounce pool since tilegx will often
306# have more than 4GB of memory, but we don't currently use the IOTLB to present
307# a 32-bit address to OHCI. So we need to use a bounce pool instead.
ffecfd1a
DW
308config NEED_BOUNCE_POOL
309 bool
debeb297 310 default y if TILE && USB_OHCI_HCD
ffecfd1a 311
6225e937
CL
312config NR_QUICK
313 int
314 depends on QUICKLIST
0176bd3d 315 default "2" if AVR32
6225e937 316 default "1"
f057eac0
SR
317
318config VIRT_TO_BUS
4febd95a
SR
319 bool
320 help
321 An architecture should select this if it implements the
322 deprecated interface virt_to_bus(). All new architectures
323 should probably not select this.
324
cddb8a5c
AA
325
326config MMU_NOTIFIER
327 bool
83fe27ea 328 select SRCU
fc4d5c29 329
f8af4da3
HD
330config KSM
331 bool "Enable KSM for page merging"
332 depends on MMU
333 help
334 Enable Kernel Samepage Merging: KSM periodically scans those areas
335 of an application's address space that an app has advised may be
336 mergeable. When it finds pages of identical content, it replaces
d0f209f6 337 the many instances by a single page with that content, so
f8af4da3
HD
338 saving memory until one or another app needs to modify the content.
339 Recommended for use with KVM, or with other duplicative applications.
c73602ad
HD
340 See Documentation/vm/ksm.txt for more information: KSM is inactive
341 until a program has madvised that an area is MADV_MERGEABLE, and
342 root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).
f8af4da3 343
e0a94c2a
CL
344config DEFAULT_MMAP_MIN_ADDR
345 int "Low address space to protect from user allocation"
6e141546 346 depends on MMU
e0a94c2a
CL
347 default 4096
348 help
349 This is the portion of low virtual memory which should be protected
350 from userspace allocation. Keeping a user from writing to low pages
351 can help reduce the impact of kernel NULL pointer bugs.
352
353 For most ia64, ppc64 and x86 users with lots of address space
354 a value of 65536 is reasonable and should cause no problems.
355 On arm and other archs it should not be higher than 32768.
788084ab
EP
356 Programs which use vm86 functionality or have some need to map
357 this low address space will need CAP_SYS_RAWIO or disable this
358 protection by setting the value to 0.
e0a94c2a
CL
359
360 This value can be changed after boot using the
361 /proc/sys/vm/mmap_min_addr tunable.
362
d949f36f
LT
363config ARCH_SUPPORTS_MEMORY_FAILURE
364 bool
e0a94c2a 365
6a46079c
AK
366config MEMORY_FAILURE
367 depends on MMU
d949f36f 368 depends on ARCH_SUPPORTS_MEMORY_FAILURE
6a46079c 369 bool "Enable recovery from hardware memory errors"
ee6f509c 370 select MEMORY_ISOLATION
97f0b134 371 select RAS
6a46079c
AK
372 help
373 Enables code to recover from some memory failures on systems
374 with MCA recovery. This allows a system to continue running
375 even when some of its memory has uncorrected errors. This requires
376 special hardware support and typically ECC memory.
377
cae681fc 378config HWPOISON_INJECT
413f9efb 379 tristate "HWPoison pages injector"
27df5068 380 depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS
478c5ffc 381 select PROC_PAGE_MONITOR
cae681fc 382
fc4d5c29
DH
383config NOMMU_INITIAL_TRIM_EXCESS
384 int "Turn on mmap() excess space trimming before booting"
385 depends on !MMU
386 default 1
387 help
388 The NOMMU mmap() frequently needs to allocate large contiguous chunks
389 of memory on which to store mappings, but it can only ask the system
390 allocator for chunks in 2^N*PAGE_SIZE amounts - which is frequently
391 more than it requires. To deal with this, mmap() is able to trim off
392 the excess and return it to the allocator.
393
394 If trimming is enabled, the excess is trimmed off and returned to the
395 system allocator, which can cause extra fragmentation, particularly
396 if there are a lot of transient processes.
397
398 If trimming is disabled, the excess is kept, but not used, which for
399 long-term mappings means that the space is wasted.
400
401 Trimming can be dynamically controlled through a sysctl option
402 (/proc/sys/vm/nr_trim_pages) which specifies the minimum number of
403 excess pages there must be before trimming should occur, or zero if
404 no trimming is to occur.
405
406 This option specifies the initial value of this option. The default
407 of 1 says that all excess pages should be trimmed.
408
409 See Documentation/nommu-mmap.txt for more information.
bbddff05 410
4c76d9d1 411config TRANSPARENT_HUGEPAGE
13ece886 412 bool "Transparent Hugepage Support"
15626062 413 depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE
5d689240 414 select COMPACTION
57578c2e 415 select RADIX_TREE_MULTIORDER
4c76d9d1
AA
416 help
417 Transparent Hugepages allows the kernel to use huge pages and
418 huge tlb transparently to the applications whenever possible.
419 This feature can improve computing performance to certain
420 applications by speeding up page faults during memory
421 allocation, by reducing the number of tlb misses and by speeding
422 up the pagetable walking.
423
424 If memory constrained on embedded, you may want to say N.
425
13ece886
AA
426choice
427 prompt "Transparent Hugepage Support sysfs defaults"
428 depends on TRANSPARENT_HUGEPAGE
429 default TRANSPARENT_HUGEPAGE_ALWAYS
430 help
431 Selects the sysfs defaults for Transparent Hugepage Support.
432
433 config TRANSPARENT_HUGEPAGE_ALWAYS
434 bool "always"
435 help
436 Enabling Transparent Hugepage always, can increase the
437 memory footprint of applications without a guaranteed
438 benefit but it will work automatically for all applications.
439
440 config TRANSPARENT_HUGEPAGE_MADVISE
441 bool "madvise"
442 help
443 Enabling Transparent Hugepage madvise, will only provide a
444 performance improvement benefit to the applications using
445 madvise(MADV_HUGEPAGE) but it won't risk to increase the
446 memory footprint of applications without a guaranteed
447 benefit.
448endchoice
449
e496cf3d
KS
450#
451# We don't deposit page tables on file THP mapping,
452# but Power makes use of them to address MMU quirk.
453#
454config TRANSPARENT_HUGE_PAGECACHE
455 def_bool y
456 depends on TRANSPARENT_HUGEPAGE && !PPC
457
bbddff05
TH
458#
459# UP and nommu archs use km based percpu allocator
460#
461config NEED_PER_CPU_KM
462 depends on !SMP
463 bool
464 default y
077b1f83
DM
465
466config CLEANCACHE
467 bool "Enable cleancache driver to cache clean pages if tmem is present"
468 default n
469 help
470 Cleancache can be thought of as a page-granularity victim cache
471 for clean pages that the kernel's pageframe replacement algorithm
472 (PFRA) would like to keep around, but can't since there isn't enough
473 memory. So when the PFRA "evicts" a page, it first attempts to use
140a1ef2 474 cleancache code to put the data contained in that page into
077b1f83
DM
475 "transcendent memory", memory that is not directly accessible or
476 addressable by the kernel and is of unknown and possibly
477 time-varying size. And when a cleancache-enabled
478 filesystem wishes to access a page in a file on disk, it first
479 checks cleancache to see if it already contains it; if it does,
480 the page is copied into the kernel and a disk access is avoided.
481 When a transcendent memory driver is available (such as zcache or
482 Xen transcendent memory), a significant I/O reduction
483 may be achieved. When none is available, all cleancache calls
484 are reduced to a single pointer-compare-against-NULL resulting
485 in a negligible performance hit.
486
487 If unsure, say Y to enable cleancache
27c6aec2
DM
488
489config FRONTSWAP
490 bool "Enable frontswap to cache swap pages if tmem is present"
491 depends on SWAP
492 default n
493 help
494 Frontswap is so named because it can be thought of as the opposite
495 of a "backing" store for a swap device. The data is stored into
496 "transcendent memory", memory that is not directly accessible or
497 addressable by the kernel and is of unknown and possibly
498 time-varying size. When space in transcendent memory is available,
499 a significant swap I/O reduction may be achieved. When none is
500 available, all frontswap calls are reduced to a single pointer-
501 compare-against-NULL resulting in a negligible performance hit
502 and swap data is stored as normal on the matching swap device.
503
504 If unsure, say Y to enable frontswap.
f825c736
AK
505
506config CMA
507 bool "Contiguous Memory Allocator"
de32a817 508 depends on HAVE_MEMBLOCK && MMU
f825c736
AK
509 select MIGRATION
510 select MEMORY_ISOLATION
511 help
512 This enables the Contiguous Memory Allocator which allows other
513 subsystems to allocate big physically-contiguous blocks of memory.
514 CMA reserves a region of memory and allows only movable pages to
515 be allocated from it. This way, the kernel can use the memory for
516 pagecache and when a subsystem requests for contiguous area, the
517 allocated pages are migrated away to serve the contiguous request.
518
519 If unsure, say "n".
520
521config CMA_DEBUG
522 bool "CMA debug messages (DEVELOPMENT)"
523 depends on DEBUG_KERNEL && CMA
524 help
525 Turns on debug messages in CMA. This produces KERN_DEBUG
526 messages for every CMA call as well as various messages while
527 processing calls such as dma_alloc_from_contiguous().
528 This option does not affect warning and error messages.
bf550fc9 529
28b24c1f
SL
530config CMA_DEBUGFS
531 bool "CMA debugfs interface"
532 depends on CMA && DEBUG_FS
533 help
534 Turns on the DebugFS interface for CMA.
535
a254129e
JK
536config CMA_AREAS
537 int "Maximum count of the CMA areas"
538 depends on CMA
539 default 7
540 help
541 CMA allows to create CMA areas for particular purpose, mainly,
542 used as device private area. This parameter sets the maximum
543 number of CMA area in the system.
544
545 If unsure, leave the default value "7".
546
af8d417a
DS
547config MEM_SOFT_DIRTY
548 bool "Track memory changes"
549 depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS
550 select PROC_PAGE_MONITOR
4e2e2770 551 help
af8d417a
DS
552 This option enables memory changes tracking by introducing a
553 soft-dirty bit on pte-s. This bit it set when someone writes
554 into a page just as regular dirty bit, but unlike the latter
555 it can be cleared by hands.
556
557 See Documentation/vm/soft-dirty.txt for more details.
4e2e2770 558
2b281117
SJ
559config ZSWAP
560 bool "Compressed cache for swap pages (EXPERIMENTAL)"
561 depends on FRONTSWAP && CRYPTO=y
562 select CRYPTO_LZO
12d79d64 563 select ZPOOL
2b281117
SJ
564 default n
565 help
566 A lightweight compressed cache for swap pages. It takes
567 pages that are in the process of being swapped out and attempts to
568 compress them into a dynamically allocated RAM-based memory pool.
569 This can result in a significant I/O reduction on swap device and,
570 in the case where decompressing from RAM is faster that swap device
571 reads, can also improve workload performance.
572
573 This is marked experimental because it is a new feature (as of
574 v3.11) that interacts heavily with memory reclaim. While these
575 interactions don't cause any known issues on simple memory setups,
576 they have not be fully explored on the large set of potential
577 configurations and workloads that exist.
578
af8d417a
DS
579config ZPOOL
580 tristate "Common API for compressed memory storage"
581 default n
0f8975ec 582 help
af8d417a
DS
583 Compressed memory storage API. This allows using either zbud or
584 zsmalloc.
0f8975ec 585
af8d417a 586config ZBUD
9a001fc1 587 tristate "Low (Up to 2x) density storage for compressed pages"
af8d417a
DS
588 default n
589 help
590 A special purpose allocator for storing compressed pages.
591 It is designed to store up to two compressed pages per physical
592 page. While this design limits storage density, it has simple and
593 deterministic reclaim properties that make it preferable to a higher
594 density approach when reclaim will be used.
bcf1647d 595
9a001fc1
VW
596config Z3FOLD
597 tristate "Up to 3x density storage for compressed pages"
598 depends on ZPOOL
599 default n
600 help
601 A special purpose allocator for storing compressed pages.
602 It is designed to store up to three compressed pages per physical
603 page. It is a ZBUD derivative so the simplicity and determinism are
604 still there.
605
bcf1647d 606config ZSMALLOC
d867f203 607 tristate "Memory allocator for compressed pages"
bcf1647d
MK
608 depends on MMU
609 default n
610 help
611 zsmalloc is a slab-based memory allocator designed to store
612 compressed RAM pages. zsmalloc uses virtual memory mapping
613 in order to reduce fragmentation. However, this results in a
614 non-standard allocator interface where a handle, not a pointer, is
615 returned by an alloc(). This handle must be mapped in order to
616 access the allocated space.
617
618config PGTABLE_MAPPING
619 bool "Use page table mapping to access object in zsmalloc"
620 depends on ZSMALLOC
621 help
622 By default, zsmalloc uses a copy-based object mapping method to
623 access allocations that span two pages. However, if a particular
624 architecture (ex, ARM) performs VM mapping faster than copying,
625 then you should select this. This causes zsmalloc to use page table
626 mapping rather than copying for object mapping.
627
2216ee85
BH
628 You can check speed with zsmalloc benchmark:
629 https://github.com/spartacus06/zsmapbench
9e5c33d7 630
0f050d99
GM
631config ZSMALLOC_STAT
632 bool "Export zsmalloc statistics"
633 depends on ZSMALLOC
634 select DEBUG_FS
635 help
636 This option enables code in the zsmalloc to collect various
637 statistics about whats happening in zsmalloc and exports that
638 information to userspace via debugfs.
639 If unsure, say N.
640
9e5c33d7
MS
641config GENERIC_EARLY_IOREMAP
642 bool
042d27ac
HD
643
644config MAX_STACK_SIZE_MB
645 int "Maximum user stack size for 32-bit processes (MB)"
646 default 80
647 range 8 256 if METAG
648 range 8 2048
649 depends on STACK_GROWSUP && (!64BIT || COMPAT)
650 help
651 This is the maximum stack size in Megabytes in the VM layout of 32-bit
652 user processes when the stack grows upwards (currently only on parisc
653 and metag arch). The stack will be located at the highest memory
654 address minus the given value, unless the RLIMIT_STACK hard limit is
655 changed to a smaller value in which case that is used.
656
657 A sane initial value is 80 MB.
3a80a7fa
MG
658
659# For architectures that support deferred memory initialisation
660config ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT
661 bool
662
663config DEFERRED_STRUCT_PAGE_INIT
1ce22103 664 bool "Defer initialisation of struct pages to kthreads"
3a80a7fa
MG
665 default n
666 depends on ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT
11e68567 667 depends on NO_BOOTMEM && MEMORY_HOTPLUG
95794924 668 depends on !FLATMEM
3a80a7fa
MG
669 help
670 Ordinarily all struct pages are initialised during early boot in a
671 single thread. On very large machines this can take a considerable
672 amount of time. If this option is set, large machines will bring up
673 a subset of memmap at boot and then initialise the rest in parallel
1ce22103
VB
674 by starting one-off "pgdatinitX" kernel thread for each node X. This
675 has a potential performance impact on processes running early in the
676 lifetime of the system until these kthreads finish the
677 initialisation.
033fbae9 678
33c3fc71
VD
679config IDLE_PAGE_TRACKING
680 bool "Enable idle page tracking"
681 depends on SYSFS && MMU
682 select PAGE_EXTENSION if !64BIT
683 help
684 This feature allows to estimate the amount of user pages that have
685 not been touched during a given period of time. This information can
686 be useful to tune memory cgroup limits and/or for job placement
687 within a compute cluster.
688
689 See Documentation/vm/idle_page_tracking.txt for more details.
690
033fbae9 691config ZONE_DEVICE
c02b6aec 692 bool "Device memory (pmem, etc...) hotplug support"
033fbae9
DW
693 depends on MEMORY_HOTPLUG
694 depends on MEMORY_HOTREMOVE
99490f16 695 depends on SPARSEMEM_VMEMMAP
033fbae9
DW
696 depends on X86_64 #arch_add_memory() comprehends device memory
697
698 help
699 Device memory hotplug support allows for establishing pmem,
700 or other device driver discovered memory regions, in the
701 memmap. This allows pfn_to_page() lookups of otherwise
702 "device-physical" addresses which is needed for using a DAX
703 mapping in an O_DIRECT operation, among other things.
704
705 If FS_DAX is enabled, then say Y.
06a660ad 706
8025e5dd
JK
707config FRAME_VECTOR
708 bool
63c17fb8
DH
709
710config ARCH_USES_HIGH_VMA_FLAGS
711 bool
66d37570
DH
712config ARCH_HAS_PKEYS
713 bool