Kconfig 8.2 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 70 71
config SPARSEMEM
	def_bool y
	depends on SPARSEMEM_MANUAL

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

config SPARSEMEM_VMEMMAP
119 120 121 122 123 124 125
	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.
126

127 128 129
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
	bool "Allow for memory hot-add"
130
	depends on SPARSEMEM || X86_64_ACPI_NUMA
131
	depends on HOTPLUG && !(HIBERNATION && !S390) && ARCH_ENABLE_MEMORY_HOTPLUG
132
	depends on (IA64 || X86 || PPC64 || SUPERH || S390)
133 134

comment "Memory hotplug is currently incompatible with Software Suspend"
135
	depends on SPARSEMEM && HOTPLUG && HIBERNATION && !S390
136

137 138 139 140
config MEMORY_HOTPLUG_SPARSE
	def_bool y
	depends on SPARSEMEM && MEMORY_HOTPLUG

K
KAMEZAWA Hiroyuki 已提交
141 142 143 144 145
config MEMORY_HOTREMOVE
	bool "Allow for memory hot remove"
	depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
	depends on MIGRATION

146 147 148 149 150 151 152 153 154 155
#
# 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
156
	depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM
157

H
Hugh Dickins 已提交
158 159 160 161 162
# 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.
163
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
H
Hugh Dickins 已提交
164 165 166 167
#
config SPLIT_PTLOCK_CPUS
	int
	default "4096" if ARM && !CPU_CACHE_VIPT
168
	default "4096" if PARISC && !PA20
H
Hugh Dickins 已提交
169
	default "4"
170 171 172 173 174

#
# support for page migration
#
config MIGRATION
C
Christoph Lameter 已提交
175
	bool "Page migration"
176
	def_bool y
177
	depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE
C
Christoph Lameter 已提交
178 179 180 181 182
	help
	  Allows the migration of the physical location of pages of processes
	  while the virtual addresses are not changed. This is useful for
	  example on NUMA systems to put pages nearer to the processors accessing
	  the page.
183

184 185 186
config PHYS_ADDR_T_64BIT
	def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT

187 188 189 190 191
config ZONE_DMA_FLAG
	int
	default "0" if !ZONE_DMA
	default "1"

192 193 194 195
config BOUNCE
	def_bool y
	depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)

196 197 198
config NR_QUICK
	int
	depends on QUICKLIST
199
	default "2" if SUPERH || AVR32
200
	default "1"
S
Stephen Rothwell 已提交
201 202 203 204

config VIRT_TO_BUS
	def_bool y
	depends on !ARCH_NO_VIRT_TO_BUS
A
Andrea Arcangeli 已提交
205

206 207 208 209 210 211
config HAVE_MLOCK
	bool
	default y if MMU=y

config HAVE_MLOCKED_PAGE_BIT
	bool
212
	default y if HAVE_MLOCK=y
213

A
Andrea Arcangeli 已提交
214 215
config MMU_NOTIFIER
	bool
216

217 218 219 220 221 222 223 224 225 226 227
config DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
        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.
228 229 230
	  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.
231 232 233 234 235

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


236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262
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.