Kconfig 24.8 KB
Newer Older
1 2 3

menu "Memory Management options"

4 5
config SELECT_MEMORY_MODEL
	def_bool y
6
	depends on ARCH_SELECT_MEMORY_MODEL
7

8 9
choice
	prompt "Memory model"
10 11
	depends on SELECT_MEMORY_MODEL
	default DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT
A
Andy Whitcroft 已提交
12
	default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT
13
	default FLATMEM_MANUAL
14

15
config FLATMEM_MANUAL
16
	bool "Flat Memory"
17
	depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE
18 19 20 21 22 23
	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: FLATMEM.  This is normal
	  and a correct option.

A
Andy Whitcroft 已提交
24 25
	  Some users of more advanced features like NUMA and
	  memory hotplug may have different options here.
G
Geert Uytterhoeven 已提交
26
	  DISCONTIGMEM is a more mature, better tested system,
A
Andy Whitcroft 已提交
27 28 29 30 31 32
	  but is incompatible with memory hotplug and may suffer
	  decreased performance over SPARSEMEM.  If unsure between
	  "Sparse Memory" and "Discontiguous Memory", choose
	  "Discontiguous Memory".

	  If unsure, choose this option (Flat Memory) over any other.
33

34
config DISCONTIGMEM_MANUAL
D
Dave Hansen 已提交
35
	bool "Discontiguous Memory"
36 37
	depends on ARCH_DISCONTIGMEM_ENABLE
	help
38 39 40 41 42
	  This option provides enhanced support for discontiguous
	  memory systems, over FLATMEM.  These systems have holes
	  in their physical address spaces, and this option provides
	  more efficient handling of these holes.  However, the vast
	  majority of hardware has quite flat address spaces, and
P
Philipp Marek 已提交
43
	  can have degraded performance from the extra overhead that
44 45 46 47
	  this option imposes.

	  Many NUMA configurations will have this as the only option.

48 49
	  If unsure, choose "Flat Memory" over this option.

A
Andy Whitcroft 已提交
50 51 52 53 54 55 56 57
config SPARSEMEM_MANUAL
	bool "Sparse Memory"
	depends on ARCH_SPARSEMEM_ENABLE
	help
	  This will be the only option for some systems, including
	  memory hotplug systems.  This is normal.

	  For many other systems, this will be an alternative to
D
Dave Hansen 已提交
58
	  "Discontiguous Memory".  This option provides some potential
A
Andy Whitcroft 已提交
59 60 61 62 63 64
	  performance benefits, along with decreased code complexity,
	  but it is newer, and more experimental.

	  If unsure, choose "Discontiguous Memory" or "Flat Memory"
	  over this option.

65 66
endchoice

67 68 69 70
config DISCONTIGMEM
	def_bool y
	depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL

A
Andy Whitcroft 已提交
71 72
config SPARSEMEM
	def_bool y
R
Russell King 已提交
73
	depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL
A
Andy Whitcroft 已提交
74

75 76
config FLATMEM
	def_bool y
A
Andy Whitcroft 已提交
77 78 79 80 81
	depends on (!DISCONTIGMEM && !SPARSEMEM) || FLATMEM_MANUAL

config FLAT_NODE_MEM_MAP
	def_bool y
	depends on !SPARSEMEM
82

83 84 85 86 87 88 89 90
#
# 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
A
Andy Whitcroft 已提交
91 92 93

config HAVE_MEMORY_PRESENT
	def_bool y
A
Andy Whitcroft 已提交
94
	depends on ARCH_HAVE_MEMORY_PRESENT || SPARSEMEM
B
Bob Picco 已提交
95

96 97
#
# SPARSEMEM_EXTREME (which is the default) does some bootmem
98
# allocations when memory_present() is called.  If this cannot
99 100 101 102 103 104 105 106
# 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
107
	bool
108

B
Bob Picco 已提交
109
#
M
Matt LaPlante 已提交
110
# Architecture platforms which require a two level mem_section in SPARSEMEM
B
Bob Picco 已提交
111 112 113
# must select this option. This is usually for architecture platforms with
# an extremely sparse physical address space.
#
114 115 116
config SPARSEMEM_EXTREME
	def_bool y
	depends on SPARSEMEM && !SPARSEMEM_STATIC
H
Hugh Dickins 已提交
117

118
config SPARSEMEM_VMEMMAP_ENABLE
119
	bool
120

121 122 123 124
config SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
	def_bool y
	depends on SPARSEMEM && X86_64

125
config SPARSEMEM_VMEMMAP
126 127 128 129 130 131 132
	bool "Sparse Memory virtual memmap"
	depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE
	default y
	help
	 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.
133

Y
Yinghai Lu 已提交
134
config HAVE_MEMBLOCK
135
	bool
Y
Yinghai Lu 已提交
136

T
Tejun Heo 已提交
137
config HAVE_MEMBLOCK_NODE_MAP
138
	bool
T
Tejun Heo 已提交
139

140
config HAVE_MEMBLOCK_PHYS_MAP
141
	bool
142

143
config HAVE_GENERIC_GUP
144
	bool
145

146
config ARCH_DISCARD_MEMBLOCK
147
	bool
148

149
config NO_BOOTMEM
150
	bool
151

152
config MEMORY_ISOLATION
153
	bool
154

155 156 157 158 159 160 161
#
# 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

162 163 164
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
	bool "Allow for memory hot-add"
165
	depends on SPARSEMEM || X86_64_ACPI_NUMA
166
	depends on ARCH_ENABLE_MEMORY_HOTPLUG
167

168 169 170 171
config MEMORY_HOTPLUG_SPARSE
	def_bool y
	depends on SPARSEMEM && MEMORY_HOTPLUG

172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187
config MEMORY_HOTPLUG_DEFAULT_ONLINE
        bool "Online the newly added memory blocks by default"
        default n
        depends on MEMORY_HOTPLUG
        help
	  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.
	  See Documentation/memory-hotplug.txt for more information.

	  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.

K
KAMEZAWA Hiroyuki 已提交
188 189
config MEMORY_HOTREMOVE
	bool "Allow for memory hot remove"
190
	select MEMORY_ISOLATION
191
	select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64)
K
KAMEZAWA Hiroyuki 已提交
192 193 194
	depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
	depends on MIGRATION

H
Hugh Dickins 已提交
195 196 197 198 199
# 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.
200
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
201
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
H
Hugh Dickins 已提交
202 203 204
#
config SPLIT_PTLOCK_CPUS
	int
205
	default "999999" if !MMU
206 207
	default "999999" if ARM && !CPU_CACHE_VIPT
	default "999999" if PARISC && !PA20
H
Hugh Dickins 已提交
208
	default "4"
209

210
config ARCH_ENABLE_SPLIT_PMD_PTLOCK
211
	bool
212

213 214 215
#
# support for memory balloon
config MEMORY_BALLOON
216
	bool
217

218 219 220 221 222
#
# support for memory balloon compaction
config BALLOON_COMPACTION
	bool "Allow for balloon memory compaction/migration"
	def_bool y
223
	depends on COMPACTION && MEMORY_BALLOON
224 225 226 227 228 229 230 231 232
	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.

233 234 235 236
#
# support for memory compaction
config COMPACTION
	bool "Allow for memory compaction"
237
	def_bool y
238
	select MIGRATION
239
	depends on MMU
240
	help
241 242 243 244 245 246 247 248
          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.
249

250 251 252 253
#
# support for page migration
#
config MIGRATION
C
Christoph Lameter 已提交
254
	bool "Page migration"
255
	def_bool y
256
	depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU
C
Christoph Lameter 已提交
257 258
	help
	  Allows the migration of the physical location of pages of processes
259 260 261 262 263
	  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.
264

265
config ARCH_ENABLE_HUGEPAGE_MIGRATION
266
	bool
267

268 269 270
config ARCH_ENABLE_THP_MIGRATION
	bool

271
config PHYS_ADDR_T_64BIT
272
	def_bool 64BIT
273

274
config BOUNCE
275 276
	bool "Enable bounce buffers"
	default y
277
	depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)
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.
283

284 285 286 287
config NR_QUICK
	int
	depends on QUICKLIST
	default "1"
S
Stephen Rothwell 已提交
288 289

config VIRT_TO_BUS
290 291 292 293 294 295
	bool
	help
	  An architecture should select this if it implements the
	  deprecated interface virt_to_bus().  All new architectures
	  should probably not select this.

A
Andrea Arcangeli 已提交
296 297 298

config MMU_NOTIFIER
	bool
299
	select SRCU
300

H
Hugh Dickins 已提交
301 302 303 304 305 306 307
config KSM
	bool "Enable KSM for page merging"
	depends on MMU
	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
308
	  the many instances by a single page with that content, so
H
Hugh Dickins 已提交
309 310
	  saving memory until one or another app needs to modify the content.
	  Recommended for use with KVM, or with other duplicative applications.
311
	  See Documentation/vm/ksm.rst for more information: KSM is inactive
H
Hugh Dickins 已提交
312 313
	  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).
H
Hugh Dickins 已提交
314

315 316
config DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
317
	depends on MMU
318 319 320 321 322 323 324 325 326
        default 4096
        help
	  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.
327 328 329
	  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.
330 331 332 333

	  This value can be changed after boot using the
	  /proc/sys/vm/mmap_min_addr tunable.

334 335
config ARCH_SUPPORTS_MEMORY_FAILURE
	bool
336

337 338
config MEMORY_FAILURE
	depends on MMU
339
	depends on ARCH_SUPPORTS_MEMORY_FAILURE
340
	bool "Enable recovery from hardware memory errors"
341
	select MEMORY_ISOLATION
342
	select RAS
343 344 345 346 347 348
	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.

349
config HWPOISON_INJECT
350
	tristate "HWPoison pages injector"
351
	depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS
W
Wu Fengguang 已提交
352
	select PROC_PAGE_MONITOR
353

354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380
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.

	  See Documentation/nommu-mmap.txt for more information.
381

382
config TRANSPARENT_HUGEPAGE
383
	bool "Transparent Hugepage Support"
384
	depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE
385
	select COMPACTION
386
	select RADIX_TREE_MULTIORDER
387 388 389 390 391 392 393 394 395 396
	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.

397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420
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

421 422 423 424 425 426 427 428 429 430 431 432
config ARCH_WANTS_THP_SWAP
       def_bool n

config THP_SWAP
	def_bool y
	depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP
	help
	  Swap transparent huge pages in one piece, without splitting.
	  XXX: For now this only does clustered swap space allocation.

	  For selection by architectures with reasonable THP sizes.

433 434
config	TRANSPARENT_HUGE_PAGECACHE
	def_bool y
435
	depends on TRANSPARENT_HUGEPAGE
436

437 438 439 440 441 442 443
#
# UP and nommu archs use km based percpu allocator
#
config NEED_PER_CPU_KM
	depends on !SMP
	bool
	default y
444 445 446 447 448 449 450 451 452

config CLEANCACHE
	bool "Enable cleancache driver to cache clean pages if tmem is present"
	default n
	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
453
	  cleancache code to put the data contained in that page into
454 455 456 457 458 459 460 461 462 463 464 465 466
	  "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
467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483

config FRONTSWAP
	bool "Enable frontswap to cache swap pages if tmem is present"
	depends on SWAP
	default n
	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.
484 485 486

config CMA
	bool "Contiguous Memory Allocator"
487
	depends on HAVE_MEMBLOCK && MMU
488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507
	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.
508

S
Sasha Levin 已提交
509 510 511 512 513 514
config CMA_DEBUGFS
	bool "CMA debugfs interface"
	depends on CMA && DEBUG_FS
	help
	  Turns on the DebugFS interface for CMA.

515 516 517 518 519 520 521 522 523 524 525
config CMA_AREAS
	int "Maximum count of the CMA areas"
	depends on CMA
	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.

	  If unsure, leave the default value "7".

526 527 528 529
config MEM_SOFT_DIRTY
	bool "Track memory changes"
	depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS
	select PROC_PAGE_MONITOR
S
Seth Jennings 已提交
530
	help
531 532 533 534 535
	  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.

536
	  See Documentation/admin-guide/mm/soft-dirty.rst for more details.
S
Seth Jennings 已提交
537

S
Seth Jennings 已提交
538 539 540 541
config ZSWAP
	bool "Compressed cache for swap pages (EXPERIMENTAL)"
	depends on FRONTSWAP && CRYPTO=y
	select CRYPTO_LZO
542
	select ZPOOL
S
Seth Jennings 已提交
543 544 545 546 547 548 549 550 551 552 553 554 555 556 557
	default n
	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.

558 559 560
config ZPOOL
	tristate "Common API for compressed memory storage"
	default n
561
	help
562 563
	  Compressed memory storage API.  This allows using either zbud or
	  zsmalloc.
564

565
config ZBUD
566
	tristate "Low (Up to 2x) density storage for compressed pages"
567 568 569 570 571 572 573
	default n
	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.
M
Minchan Kim 已提交
574

575 576 577 578 579 580 581 582 583 584
config Z3FOLD
	tristate "Up to 3x density storage for compressed pages"
	depends on ZPOOL
	default n
	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.

M
Minchan Kim 已提交
585
config ZSMALLOC
586
	tristate "Memory allocator for compressed pages"
M
Minchan Kim 已提交
587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606
	depends on MMU
	default n
	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.

config PGTABLE_MAPPING
	bool "Use page table mapping to access object in zsmalloc"
	depends on ZSMALLOC
	help
	  By default, zsmalloc uses a copy-based object mapping method to
	  access allocations that span two pages. However, if a particular
	  architecture (ex, ARM) performs VM mapping faster than copying,
	  then you should select this. This causes zsmalloc to use page table
	  mapping rather than copying for object mapping.

607 608
	  You can check speed with zsmalloc benchmark:
	  https://github.com/spartacus06/zsmapbench
609

610 611 612 613 614 615 616 617 618 619
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.

620 621
config GENERIC_EARLY_IOREMAP
	bool
622 623 624 625 626 627 628 629 630

config MAX_STACK_SIZE_MB
	int "Maximum user stack size for 32-bit processes (MB)"
	default 80
	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
J
James Hogan 已提交
631 632 633
	  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.
634 635

	  A sane initial value is 80 MB.
636 637

config DEFERRED_STRUCT_PAGE_INIT
638
	bool "Defer initialisation of struct pages to kthreads"
639
	default n
640
	depends on NO_BOOTMEM
641
	depends on !FLATMEM
642
	depends on !NEED_PER_CPU_KM
643 644 645 646 647
	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
	  a subset of memmap at boot and then initialise the rest in parallel
648 649 650 651
	  by starting one-off "pgdatinitX" kernel thread for each node X. This
	  has a potential performance impact on processes running early in the
	  lifetime of the system until these kthreads finish the
	  initialisation.
652

653 654 655 656 657 658 659 660 661 662
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.

663 664
	  See Documentation/admin-guide/mm/idle_page_tracking.rst for
	  more details.
665

666 667 668 669
# arch_add_memory() comprehends device memory
config ARCH_HAS_ZONE_DEVICE
	bool

670
config ZONE_DEVICE
671
	bool "Device memory (pmem, HMM, etc...) hotplug support"
672 673
	depends on MEMORY_HOTPLUG
	depends on MEMORY_HOTREMOVE
674
	depends on SPARSEMEM_VMEMMAP
675
	depends on ARCH_HAS_ZONE_DEVICE
676
	select RADIX_TREE_MULTIORDER
677 678 679 680 681 682 683 684 685

	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.
686

687 688 689 690 691 692 693 694 695 696
config ARCH_HAS_HMM
	bool
	default y
	depends on (X86_64 || PPC64)
	depends on ZONE_DEVICE
	depends on MMU && 64BIT
	depends on MEMORY_HOTPLUG
	depends on MEMORY_HOTREMOVE
	depends on SPARSEMEM_VMEMMAP

697 698 699
config MIGRATE_VMA_HELPER
	bool

700 701 702
config DEV_PAGEMAP_OPS
	bool

703 704
config HMM
	bool
705
	select MIGRATE_VMA_HELPER
706

707 708 709 710 711 712 713 714 715 716 717 718
config HMM_MIRROR
	bool "HMM mirror CPU page table into a device page table"
	depends on ARCH_HAS_HMM
	select MMU_NOTIFIER
	select HMM
	help
	  Select HMM_MIRROR if you want to mirror range of the CPU page table of a
	  process into a device page table. Here, mirror means "keep synchronized".
	  Prerequisites: the device must provide the ability to write-protect its
	  page tables (at PAGE_SIZE granularity), and must be able to recover from
	  the resulting potential page faults.

719 720 721
config DEVICE_PRIVATE
	bool "Unaddressable device memory (GPU memory, ...)"
	depends on ARCH_HAS_HMM
722
	select HMM
723
	select DEV_PAGEMAP_OPS
724 725 726 727 728 729

	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.

730 731 732 733
config DEVICE_PUBLIC
	bool "Addressable device memory (like GPU memory)"
	depends on ARCH_HAS_HMM
	select HMM
734
	select DEV_PAGEMAP_OPS
735 736 737 738 739 740

	help
	  Allows creation of struct pages to represent addressable device
	  memory; i.e., memory that is accessible from both the device and
	  the CPU

741 742
config FRAME_VECTOR
	bool
743 744 745

config ARCH_USES_HIGH_VMA_FLAGS
	bool
746 747
config ARCH_HAS_PKEYS
	bool
748 749 750 751 752 753 754 755

config PERCPU_STATS
	bool "Collect percpu memory statistics"
	default n
	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.
756 757 758 759 760 761 762 763 764

config GUP_BENCHMARK
	bool "Enable infrastructure for get_user_pages_fast() benchmarking"
	default n
	help
	  Provides /sys/kernel/debug/gup_benchmark that helps with testing
	  performance of get_user_pages_fast().

	  See tools/testing/selftests/vm/gup_benchmark.c
765 766 767

config ARCH_HAS_PTE_SPECIAL
	bool
768 769

endmenu