Blame view
mm/Kconfig
12.4 KB
e1785e85b
|
1 2 3 |
config SELECT_MEMORY_MODEL def_bool y depends on EXPERIMENTAL || ARCH_SELECT_MEMORY_MODEL |
3a9da7655
|
4 5 |
choice prompt "Memory model" |
e1785e85b
|
6 7 |
depends on SELECT_MEMORY_MODEL default DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT |
d41dee369
|
8 |
default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT |
e1785e85b
|
9 |
default FLATMEM_MANUAL |
3a9da7655
|
10 |
|
e1785e85b
|
11 |
config FLATMEM_MANUAL |
3a9da7655
|
12 |
bool "Flat Memory" |
c898ec16e
|
13 |
depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE |
3a9da7655
|
14 15 16 17 18 |
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. |
d41dee369
|
19 20 21 22 23 24 25 26 27 |
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. |
3a9da7655
|
28 |
|
e1785e85b
|
29 |
config DISCONTIGMEM_MANUAL |
f3519f919
|
30 |
bool "Discontiguous Memory" |
3a9da7655
|
31 32 |
depends on ARCH_DISCONTIGMEM_ENABLE help |
785dcd44b
|
33 34 35 36 37 |
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 |
ad3d0a382
|
38 |
can have degraded performance from the extra overhead that |
785dcd44b
|
39 40 41 |
this option imposes. Many NUMA configurations will have this as the only option. |
3a9da7655
|
42 |
If unsure, choose "Flat Memory" over this option. |
d41dee369
|
43 44 45 46 47 48 49 50 |
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 |
f3519f919
|
51 |
"Discontiguous Memory". This option provides some potential |
d41dee369
|
52 53 54 55 56 |
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. |
3a9da7655
|
57 |
endchoice |
e1785e85b
|
58 59 60 |
config DISCONTIGMEM def_bool y depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL |
d41dee369
|
61 62 |
config SPARSEMEM def_bool y |
1a83e175d
|
63 |
depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL |
d41dee369
|
64 |
|
e1785e85b
|
65 66 |
config FLATMEM def_bool y |
d41dee369
|
67 68 69 70 71 |
depends on (!DISCONTIGMEM && !SPARSEMEM) || FLATMEM_MANUAL config FLAT_NODE_MEM_MAP def_bool y depends on !SPARSEMEM |
e1785e85b
|
72 |
|
93b7504e3
|
73 74 75 76 77 78 79 80 |
# # 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 |
af705362a
|
81 82 83 |
config HAVE_MEMORY_PRESENT def_bool y |
d41dee369
|
84 |
depends on ARCH_HAVE_MEMORY_PRESENT || SPARSEMEM |
802f192e4
|
85 86 |
# |
3e347261a
|
87 |
# SPARSEMEM_EXTREME (which is the default) does some bootmem |
84eb8d060
|
88 |
# allocations when memory_present() is called. If this cannot |
3e347261a
|
89 90 91 92 93 94 95 96 |
# 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 |
9ba16087d
|
97 |
bool |
3e347261a
|
98 99 |
# |
44c09201a
|
100 |
# Architecture platforms which require a two level mem_section in SPARSEMEM |
802f192e4
|
101 102 103 |
# must select this option. This is usually for architecture platforms with # an extremely sparse physical address space. # |
3e347261a
|
104 105 106 |
config SPARSEMEM_EXTREME def_bool y depends on SPARSEMEM && !SPARSEMEM_STATIC |
4c21e2f24
|
107 |
|
29c71111d
|
108 |
config SPARSEMEM_VMEMMAP_ENABLE |
9ba16087d
|
109 |
bool |
29c71111d
|
110 |
|
9bdac9142
|
111 112 113 |
config SPARSEMEM_ALLOC_MEM_MAP_TOGETHER def_bool y depends on SPARSEMEM && X86_64 |
29c71111d
|
114 |
config SPARSEMEM_VMEMMAP |
a5ee6daa5
|
115 116 117 118 119 120 121 |
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. |
29c71111d
|
122 |
|
95f72d1ed
|
123 124 |
config HAVE_MEMBLOCK boolean |
7c0caeb86
|
125 126 |
config HAVE_MEMBLOCK_NODE_MAP boolean |
c378ddd53
|
127 128 |
config ARCH_DISCARD_MEMBLOCK boolean |
666167205
|
129 130 |
config NO_BOOTMEM boolean |
3947be196
|
131 132 133 |
# eventually, we can have this option just 'select SPARSEMEM' config MEMORY_HOTPLUG bool "Allow for memory hot-add" |
ec69acbb1
|
134 |
depends on SPARSEMEM || X86_64_ACPI_NUMA |
6ad696d2c
|
135 |
depends on HOTPLUG && ARCH_ENABLE_MEMORY_HOTPLUG |
ed84a07a1
|
136 |
depends on (IA64 || X86 || PPC_BOOK3S_64 || SUPERH || S390) |
3947be196
|
137 |
|
ec69acbb1
|
138 139 140 |
config MEMORY_HOTPLUG_SPARSE def_bool y depends on SPARSEMEM && MEMORY_HOTPLUG |
0c0e61958
|
141 142 143 144 |
config MEMORY_HOTREMOVE bool "Allow for memory hot remove" depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE depends on MIGRATION |
e20b8cca7
|
145 146 147 148 149 150 151 152 153 154 |
# # 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 |
a269cca99
|
155 |
depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM |
e20b8cca7
|
156 |
|
4c21e2f24
|
157 158 159 160 161 |
# 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. |
7b6ac9dff
|
162 |
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes. |
a70caa8ba
|
163 |
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page. |
4c21e2f24
|
164 165 166 |
# config SPLIT_PTLOCK_CPUS int |
a70caa8ba
|
167 168 169 |
default "999999" if ARM && !CPU_CACHE_VIPT default "999999" if PARISC && !PA20 default "999999" if DEBUG_SPINLOCK || DEBUG_LOCK_ALLOC |
4c21e2f24
|
170 |
default "4" |
7cbe34cf8
|
171 172 |
# |
e9e96b39f
|
173 174 175 176 |
# support for memory compaction config COMPACTION bool "Allow for memory compaction" select MIGRATION |
33a938774
|
177 |
depends on MMU |
e9e96b39f
|
178 179 180 181 |
help Allows the compaction of memory for the allocation of huge pages. # |
7cbe34cf8
|
182 183 184 |
# support for page migration # config MIGRATION |
b20a35035
|
185 |
bool "Page migration" |
6c5240ae7
|
186 |
def_bool y |
152e0659f
|
187 |
depends on NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION |
b20a35035
|
188 189 |
help Allows the migration of the physical location of pages of processes |
e9e96b39f
|
190 191 192 193 194 |
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. |
6550e07f4
|
195 |
|
600715dcd
|
196 197 |
config PHYS_ADDR_T_64BIT def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT |
4b51d6698
|
198 199 200 201 |
config ZONE_DMA_FLAG int default "0" if !ZONE_DMA default "1" |
2a7326b5b
|
202 203 204 |
config BOUNCE def_bool y depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM) |
6225e9373
|
205 206 207 |
config NR_QUICK int depends on QUICKLIST |
0176bd3da
|
208 |
default "2" if AVR32 |
6225e9373
|
209 |
default "1" |
f057eac0d
|
210 211 212 213 |
config VIRT_TO_BUS def_bool y depends on !ARCH_NO_VIRT_TO_BUS |
cddb8a5c1
|
214 215 216 |
config MMU_NOTIFIER bool |
fc4d5c292
|
217 |
|
f8af4da3b
|
218 219 220 221 222 223 224 |
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 |
d0f209f68
|
225 |
the many instances by a single page with that content, so |
f8af4da3b
|
226 227 |
saving memory until one or another app needs to modify the content. Recommended for use with KVM, or with other duplicative applications. |
c73602ad3
|
228 229 230 |
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). |
f8af4da3b
|
231 |
|
e0a94c2a6
|
232 233 |
config DEFAULT_MMAP_MIN_ADDR int "Low address space to protect from user allocation" |
6e1415467
|
234 |
depends on MMU |
e0a94c2a6
|
235 236 237 238 239 240 241 242 243 |
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. |
788084aba
|
244 245 246 |
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. |
e0a94c2a6
|
247 248 249 |
This value can be changed after boot using the /proc/sys/vm/mmap_min_addr tunable. |
d949f36f1
|
250 251 |
config ARCH_SUPPORTS_MEMORY_FAILURE bool |
e0a94c2a6
|
252 |
|
6a46079cf
|
253 254 |
config MEMORY_FAILURE depends on MMU |
d949f36f1
|
255 |
depends on ARCH_SUPPORTS_MEMORY_FAILURE |
6a46079cf
|
256 257 258 259 260 261 |
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. |
cae681fc1
|
262 |
config HWPOISON_INJECT |
413f9efbc
|
263 |
tristate "HWPoison pages injector" |
27df5068e
|
264 |
depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS |
478c5ffc0
|
265 |
select PROC_PAGE_MONITOR |
cae681fc1
|
266 |
|
fc4d5c292
|
267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 |
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. |
bbddff054
|
294 |
|
4c76d9d1f
|
295 |
config TRANSPARENT_HUGEPAGE |
13ece886d
|
296 |
bool "Transparent Hugepage Support" |
f2d6bfe9f
|
297 |
depends on X86 && MMU |
5d6892407
|
298 |
select COMPACTION |
4c76d9d1f
|
299 300 301 302 303 304 305 306 307 |
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. |
13ece886d
|
308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 |
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 |
bbddff054
|
331 332 333 334 335 336 337 |
# # UP and nommu archs use km based percpu allocator # config NEED_PER_CPU_KM depends on !SMP bool default y |
077b1f83a
|
338 339 340 341 342 343 344 345 346 |
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 |
140a1ef2f
|
347 |
cleancache code to put the data contained in that page into |
077b1f83a
|
348 349 350 351 352 353 354 355 356 357 358 359 360 |
"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 |