Kconfig 12.4 KB
Newer Older
1 2 3 4
config SELECT_MEMORY_MODEL
	def_bool y
	depends on EXPERIMENTAL || ARCH_SELECT_MEMORY_MODEL

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
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
	bool "Allow for memory hot-add"
146
	depends on SPARSEMEM || X86_64_ACPI_NUMA
147
	depends on HOTPLUG && ARCH_ENABLE_MEMORY_HOTPLUG
148
	depends on (IA64 || X86 || PPC_BOOK3S_64 || SUPERH || S390)
149

150 151 152 153
config MEMORY_HOTPLUG_SPARSE
	def_bool y
	depends on SPARSEMEM && MEMORY_HOTPLUG

K
KAMEZAWA Hiroyuki 已提交
154 155 156 157 158
config MEMORY_HOTREMOVE
	bool "Allow for memory hot remove"
	depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
	depends on MIGRATION

159 160 161 162 163 164 165 166 167 168
#
# 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
169
	depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM
170

H
Hugh Dickins 已提交
171 172 173 174 175
# 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.
176
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
177
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
H
Hugh Dickins 已提交
178 179 180
#
config SPLIT_PTLOCK_CPUS
	int
181 182 183
	default "999999" if ARM && !CPU_CACHE_VIPT
	default "999999" if PARISC && !PA20
	default "999999" if DEBUG_SPINLOCK || DEBUG_LOCK_ALLOC
H
Hugh Dickins 已提交
184
	default "4"
185

186 187 188 189 190
#
# support for memory compaction
config COMPACTION
	bool "Allow for memory compaction"
	select MIGRATION
191
	depends on MMU
192 193 194
	help
	  Allows the compaction of memory for the allocation of huge pages.

195 196 197 198
#
# support for page migration
#
config MIGRATION
C
Christoph Lameter 已提交
199
	bool "Page migration"
200
	def_bool y
201
	depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION
C
Christoph Lameter 已提交
202 203
	help
	  Allows the migration of the physical location of pages of processes
204 205 206 207 208
	  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.
209

210 211 212
config PHYS_ADDR_T_64BIT
	def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT

213 214 215 216 217
config ZONE_DMA_FLAG
	int
	default "0" if !ZONE_DMA
	default "1"

218 219 220 221
config BOUNCE
	def_bool y
	depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)

222 223 224
config NR_QUICK
	int
	depends on QUICKLIST
225
	default "2" if AVR32
226
	default "1"
S
Stephen Rothwell 已提交
227 228 229 230

config VIRT_TO_BUS
	def_bool y
	depends on !ARCH_NO_VIRT_TO_BUS
A
Andrea Arcangeli 已提交
231 232 233

config MMU_NOTIFIER
	bool
234

H
Hugh Dickins 已提交
235 236 237 238 239 240 241
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
242
	  the many instances by a single page with that content, so
H
Hugh Dickins 已提交
243 244
	  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 已提交
245 246 247
	  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 已提交
248

249 250
config DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
251
	depends on MMU
252 253 254 255 256 257 258 259 260
        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.
261 262 263
	  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.
264 265 266 267

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

268 269
config ARCH_SUPPORTS_MEMORY_FAILURE
	bool
270

271 272
config MEMORY_FAILURE
	depends on MMU
273
	depends on ARCH_SUPPORTS_MEMORY_FAILURE
274 275 276 277 278 279 280
	bool "Enable recovery from hardware memory errors"
	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.

281
config HWPOISON_INJECT
282
	tristate "HWPoison pages injector"
283
	depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS
W
Wu Fengguang 已提交
284
	select PROC_PAGE_MONITOR
285

286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312
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.
313

314
config TRANSPARENT_HUGEPAGE
315
	bool "Transparent Hugepage Support"
J
Johannes Weiner 已提交
316
	depends on X86 && MMU
317
	select COMPACTION
318 319 320 321 322 323 324 325 326 327
	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.

328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351
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

352 353 354 355 356 357 358
#
# UP and nommu archs use km based percpu allocator
#
config NEED_PER_CPU_KM
	depends on !SMP
	bool
	default y
359 360 361 362 363 364 365 366 367

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
368
	  cleancache code to put the data contained in that page into
369 370 371 372 373 374 375 376 377 378 379 380 381
	  "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