Kconfig 18.7 KB
Newer Older
1 2
config SELECT_MEMORY_MODEL
	def_bool y
3
	depends on ARCH_SELECT_MEMORY_MODEL
4

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

12
config FLATMEM_MANUAL
13
	bool "Flat Memory"
14
	depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE
15 16 17 18 19 20
	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 已提交
21 22 23 24 25 26 27 28 29
	  Some users of more advanced features like NUMA and
	  memory hotplug may have different options here.
	  DISCONTIGMEM is an more mature, better tested system,
	  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.
30

31
config DISCONTIGMEM_MANUAL
D
Dave Hansen 已提交
32
	bool "Discontiguous Memory"
33 34
	depends on ARCH_DISCONTIGMEM_ENABLE
	help
35 36 37 38 39
	  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 已提交
40
	  can have degraded performance from the extra overhead that
41 42 43 44
	  this option imposes.

	  Many NUMA configurations will have this as the only option.

45 46
	  If unsure, choose "Flat Memory" over this option.

A
Andy Whitcroft 已提交
47 48 49 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
	  memory hotplug systems.  This is normal.

	  For many other systems, this will be an alternative to
D
Dave Hansen 已提交
55
	  "Discontiguous Memory".  This option provides some potential
A
Andy Whitcroft 已提交
56 57 58 59 60 61
	  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.

62 63
endchoice

64 65 66 67
config DISCONTIGMEM
	def_bool y
	depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL

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

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

config FLAT_NODE_MEM_MAP
	def_bool y
	depends on !SPARSEMEM
79

80 81 82 83 84 85 86 87
#
# 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 已提交
88 89 90

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

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

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

115
config SPARSEMEM_VMEMMAP_ENABLE
116
	bool
117

118 119 120 121
config SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
	def_bool y
	depends on SPARSEMEM && X86_64

122
config SPARSEMEM_VMEMMAP
123 124 125 126 127 128 129
	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.
130

Y
Yinghai Lu 已提交
131 132 133
config HAVE_MEMBLOCK
	boolean

T
Tejun Heo 已提交
134 135 136
config HAVE_MEMBLOCK_NODE_MAP
	boolean

137 138 139
config ARCH_DISCARD_MEMBLOCK
	boolean

140 141 142
config NO_BOOTMEM
	boolean

143 144 145
config MEMORY_ISOLATION
	boolean

146 147 148 149 150 151
config MOVABLE_NODE
	boolean "Enable to assign a node which has only movable memory"
	depends on HAVE_MEMBLOCK
	depends on NO_BOOTMEM
	depends on X86_64
	depends on NUMA
152 153 154 155 156 157 158 159 160 161 162 163
	default n
	help
	  Allow a node to have only movable memory.  Pages used by the kernel,
	  such as direct mapping pages cannot be migrated.  So the corresponding
	  memory device cannot be hotplugged.  This option allows users to
	  online all the memory of a node as movable memory so that the whole
	  node can be hotplugged.  Users who don't use the memory hotplug
	  feature are fine with this option on since they don't online memory
	  as movable.

	  Say Y here if you want to hotplug a whole node.
	  Say N here if you want kernel to use memory on all nodes evenly.
164

165 166 167 168 169 170 171
#
# 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

172 173 174
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
	bool "Allow for memory hot-add"
175
	depends on SPARSEMEM || X86_64_ACPI_NUMA
176
	depends on ARCH_ENABLE_MEMORY_HOTPLUG
177
	depends on (IA64 || X86 || PPC_BOOK3S_64 || SUPERH || S390)
178

179 180 181 182
config MEMORY_HOTPLUG_SPARSE
	def_bool y
	depends on SPARSEMEM && MEMORY_HOTPLUG

K
KAMEZAWA Hiroyuki 已提交
183 184
config MEMORY_HOTREMOVE
	bool "Allow for memory hot remove"
185 186
	select MEMORY_ISOLATION
	select HAVE_BOOTMEM_INFO_NODE if X86_64
K
KAMEZAWA Hiroyuki 已提交
187 188 189
	depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
	depends on MIGRATION

190 191 192 193 194 195 196 197 198 199
#
# If we have space for more page flags then we can enable additional
# optimizations and functionality.
#
# Regular Sparsemem takes page flag bits for the sectionid if it does not
# use a virtual memmap. Disable extended page flags for 32 bit platforms
# that require the use of a sectionid in the page flags.
#
config PAGEFLAGS_EXTENDED
	def_bool y
200
	depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM
201

H
Hugh Dickins 已提交
202 203 204 205 206
# 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.
207
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
208
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
H
Hugh Dickins 已提交
209 210 211
#
config SPLIT_PTLOCK_CPUS
	int
212 213 214
	default "999999" if ARM && !CPU_CACHE_VIPT
	default "999999" if PARISC && !PA20
	default "999999" if DEBUG_SPINLOCK || DEBUG_LOCK_ALLOC
H
Hugh Dickins 已提交
215
	default "4"
216

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

232 233 234 235
#
# support for memory compaction
config COMPACTION
	bool "Allow for memory compaction"
236
	def_bool y
237
	select MIGRATION
238
	depends on MMU
239 240 241
	help
	  Allows the compaction of memory for the allocation of huge pages.

242 243 244 245
#
# support for page migration
#
config MIGRATION
C
Christoph Lameter 已提交
246
	bool "Page migration"
247
	def_bool y
248
	depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU
C
Christoph Lameter 已提交
249 250
	help
	  Allows the migration of the physical location of pages of processes
251 252 253 254 255
	  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.
256

257 258 259
config PHYS_ADDR_T_64BIT
	def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT

260 261 262 263 264
config ZONE_DMA_FLAG
	int
	default "0" if !ZONE_DMA
	default "1"

265
config BOUNCE
266 267
	bool "Enable bounce buffers"
	default y
268
	depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)
269 270 271 272 273
	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.
274

275 276 277 278 279 280 281 282 283 284 285 286 287
# On the 'tile' arch, USB OHCI needs the bounce pool since tilegx will often
# have more than 4GB of memory, but we don't currently use the IOTLB to present
# a 32-bit address to OHCI.  So we need to use a bounce pool instead.
#
# We also use the bounce pool to provide stable page writes for jbd.  jbd
# initiates buffer writeback without locking the page or setting PG_writeback,
# and fixing that behavior (a second time; jbd2 doesn't have this problem) is
# a major rework effort.  Instead, use the bounce buffer to snapshot pages
# (until jbd goes away).  The only jbd user is ext3.
config NEED_BOUNCE_POOL
	bool
	default y if (TILE && USB_OHCI_HCD) || (BLK_DEV_INTEGRITY && JBD)

288 289 290
config NR_QUICK
	int
	depends on QUICKLIST
291
	default "2" if AVR32
292
	default "1"
S
Stephen Rothwell 已提交
293 294

config VIRT_TO_BUS
295 296 297 298 299 300
	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 已提交
301 302 303

config MMU_NOTIFIER
	bool
304

H
Hugh Dickins 已提交
305 306 307 308 309 310 311
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
312
	  the many instances by a single page with that content, so
H
Hugh Dickins 已提交
313 314
	  saving memory until one or another app needs to modify the content.
	  Recommended for use with KVM, or with other duplicative applications.
H
Hugh Dickins 已提交
315 316 317
	  See Documentation/vm/ksm.txt for more information: KSM is inactive
	  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 已提交
318

319 320
config DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
321
	depends on MMU
322 323 324 325 326 327 328 329 330
        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.
331 332 333
	  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.
334 335 336 337

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

338 339
config ARCH_SUPPORTS_MEMORY_FAILURE
	bool
340

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

352
config HWPOISON_INJECT
353
	tristate "HWPoison pages injector"
354
	depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS
W
Wu Fengguang 已提交
355
	select PROC_PAGE_MONITOR
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 381 382 383
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.
384

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

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

423 424 425 426 427 428 429 430 431 432
config CROSS_MEMORY_ATTACH
	bool "Cross Memory Support"
	depends on MMU
	default y
	help
	  Enabling this option adds the system calls process_vm_readv and
	  process_vm_writev which allow a process with the correct privileges
	  to directly read from or write to to another process's address space.
	  See the man page for more details.

433 434 435 436 437 438 439
#
# UP and nommu archs use km based percpu allocator
#
config NEED_PER_CPU_KM
	depends on !SMP
	bool
	default y
440 441 442 443 444 445 446 447 448

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
449
	  cleancache code to put the data contained in that page into
450 451 452 453 454 455 456 457 458 459 460 461 462
	  "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
463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479

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.
480 481 482

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

S
Seth Jennings 已提交
505 506 507 508 509 510 511 512 513 514
config ZBUD
	tristate
	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.

S
Seth Jennings 已提交
515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534
config ZSWAP
	bool "Compressed cache for swap pages (EXPERIMENTAL)"
	depends on FRONTSWAP && CRYPTO=y
	select CRYPTO_LZO
	select ZBUD
	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.

535 536 537 538 539 540 541 542 543 544 545
config MEM_SOFT_DIRTY
	bool "Track memory changes"
	depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY
	select PROC_PAGE_MONITOR
	help
	  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.

	  See Documentation/vm/soft-dirty.txt for more details.