Blame view
mm/Kconfig
24.8 KB
e1785e85b [PATCH] mm/Kconfi... |
1 2 |
config SELECT_MEMORY_MODEL def_bool y |
a8826eeb7 mm: remove depend... |
3 |
depends on ARCH_SELECT_MEMORY_MODEL |
e1785e85b [PATCH] mm/Kconfi... |
4 |
|
3a9da7655 [PATCH] create mm... |
5 6 |
choice prompt "Memory model" |
e1785e85b [PATCH] mm/Kconfi... |
7 8 |
depends on SELECT_MEMORY_MODEL default DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT |
d41dee369 [PATCH] sparsemem... |
9 |
default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT |
e1785e85b [PATCH] mm/Kconfi... |
10 |
default FLATMEM_MANUAL |
3a9da7655 [PATCH] create mm... |
11 |
|
e1785e85b [PATCH] mm/Kconfi... |
12 |
config FLATMEM_MANUAL |
3a9da7655 [PATCH] create mm... |
13 |
bool "Flat Memory" |
c898ec16e [PATCH] allow fla... |
14 |
depends on !(ARCH_DISCONTIGMEM_ENABLE || ARCH_SPARSEMEM_ENABLE) || ARCH_FLATMEM_ENABLE |
3a9da7655 [PATCH] create mm... |
15 16 17 18 19 |
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 [PATCH] sparsemem... |
20 21 |
Some users of more advanced features like NUMA and memory hotplug may have different options here. |
18f653327 mm/Kconfig: Gramm... |
22 |
DISCONTIGMEM is a more mature, better tested system, |
d41dee369 [PATCH] sparsemem... |
23 24 25 26 27 28 |
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 [PATCH] create mm... |
29 |
|
e1785e85b [PATCH] mm/Kconfi... |
30 |
config DISCONTIGMEM_MANUAL |
f3519f919 [PATCH] fix mm/Kc... |
31 |
bool "Discontiguous Memory" |
3a9da7655 [PATCH] create mm... |
32 33 |
depends on ARCH_DISCONTIGMEM_ENABLE help |
785dcd44b [PATCH] mm/Kconfi... |
34 35 36 37 38 |
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 small documentati... |
39 |
can have degraded performance from the extra overhead that |
785dcd44b [PATCH] mm/Kconfi... |
40 41 42 |
this option imposes. Many NUMA configurations will have this as the only option. |
3a9da7655 [PATCH] create mm... |
43 |
If unsure, choose "Flat Memory" over this option. |
d41dee369 [PATCH] sparsemem... |
44 45 46 47 48 49 50 51 |
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 [PATCH] fix mm/Kc... |
52 |
"Discontiguous Memory". This option provides some potential |
d41dee369 [PATCH] sparsemem... |
53 54 55 56 57 |
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 [PATCH] create mm... |
58 |
endchoice |
e1785e85b [PATCH] mm/Kconfi... |
59 60 61 |
config DISCONTIGMEM def_bool y depends on (!SELECT_MEMORY_MODEL && ARCH_DISCONTIGMEM_ENABLE) || DISCONTIGMEM_MANUAL |
d41dee369 [PATCH] sparsemem... |
62 63 |
config SPARSEMEM def_bool y |
1a83e175d mm: fix sparsemem... |
64 |
depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL |
d41dee369 [PATCH] sparsemem... |
65 |
|
e1785e85b [PATCH] mm/Kconfi... |
66 67 |
config FLATMEM def_bool y |
d41dee369 [PATCH] sparsemem... |
68 69 70 71 72 |
depends on (!DISCONTIGMEM && !SPARSEMEM) || FLATMEM_MANUAL config FLAT_NODE_MEM_MAP def_bool y depends on !SPARSEMEM |
e1785e85b [PATCH] mm/Kconfi... |
73 |
|
93b7504e3 [PATCH] Introduce... |
74 75 76 77 78 79 80 81 |
# # 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 [PATCH] generify ... |
82 83 84 |
config HAVE_MEMORY_PRESENT def_bool y |
d41dee369 [PATCH] sparsemem... |
85 |
depends on ARCH_HAVE_MEMORY_PRESENT || SPARSEMEM |
802f192e4 [PATCH] SPARSEMEM... |
86 87 |
# |
3e347261a [PATCH] sparsemem... |
88 |
# SPARSEMEM_EXTREME (which is the default) does some bootmem |
84eb8d060 Fix "can not" in ... |
89 |
# allocations when memory_present() is called. If this cannot |
3e347261a [PATCH] sparsemem... |
90 91 92 93 94 95 96 97 |
# 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 Kconfig: eliminat... |
98 |
bool |
3e347261a [PATCH] sparsemem... |
99 100 |
# |
44c09201a more misc typo fixes |
101 |
# Architecture platforms which require a two level mem_section in SPARSEMEM |
802f192e4 [PATCH] SPARSEMEM... |
102 103 104 |
# must select this option. This is usually for architecture platforms with # an extremely sparse physical address space. # |
3e347261a [PATCH] sparsemem... |
105 106 107 |
config SPARSEMEM_EXTREME def_bool y depends on SPARSEMEM && !SPARSEMEM_STATIC |
4c21e2f24 [PATCH] mm: split... |
108 |
|
29c71111d vmemmap: generify... |
109 |
config SPARSEMEM_VMEMMAP_ENABLE |
9ba16087d Kconfig: eliminat... |
110 |
bool |
29c71111d vmemmap: generify... |
111 |
|
9bdac9142 sparsemem: Put me... |
112 113 114 |
config SPARSEMEM_ALLOC_MEM_MAP_TOGETHER def_bool y depends on SPARSEMEM && X86_64 |
29c71111d vmemmap: generify... |
115 |
config SPARSEMEM_VMEMMAP |
a5ee6daa5 sparsemem: make S... |
116 117 118 119 120 121 122 |
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 vmemmap: generify... |
123 |
|
95f72d1ed lmb: rename to me... |
124 |
config HAVE_MEMBLOCK |
6341e62b2 kconfig: use bool... |
125 |
bool |
95f72d1ed lmb: rename to me... |
126 |
|
7c0caeb86 memblock: Add opt... |
127 |
config HAVE_MEMBLOCK_NODE_MAP |
6341e62b2 kconfig: use bool... |
128 |
bool |
7c0caeb86 memblock: Add opt... |
129 |
|
70210ed95 mm/memblock: add ... |
130 |
config HAVE_MEMBLOCK_PHYS_MAP |
6341e62b2 kconfig: use bool... |
131 |
bool |
70210ed95 mm/memblock: add ... |
132 |
|
e585513b7 x86/mm/gup: Switc... |
133 |
config HAVE_GENERIC_GUP |
6341e62b2 kconfig: use bool... |
134 |
bool |
2667f50e8 mm: introduce a g... |
135 |
|
c378ddd53 memblock, x86: Ma... |
136 |
config ARCH_DISCARD_MEMBLOCK |
6341e62b2 kconfig: use bool... |
137 |
bool |
c378ddd53 memblock, x86: Ma... |
138 |
|
666167205 memblock: add NO_... |
139 |
config NO_BOOTMEM |
6341e62b2 kconfig: use bool... |
140 |
bool |
666167205 memblock: add NO_... |
141 |
|
ee6f509c3 mm: factor out me... |
142 |
config MEMORY_ISOLATION |
6341e62b2 kconfig: use bool... |
143 |
bool |
ee6f509c3 mm: factor out me... |
144 |
|
46723bfa5 memory-hotplug: i... |
145 146 147 148 149 150 |
# # 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 |
3947be196 [PATCH] memory ho... |
151 152 153 |
# eventually, we can have this option just 'select SPARSEMEM' config MEMORY_HOTPLUG bool "Allow for memory hot-add" |
ec69acbb1 [PATCH] hot-add-m... |
154 |
depends on SPARSEMEM || X86_64_ACPI_NUMA |
40b313608 Finally eradicate... |
155 |
depends on ARCH_ENABLE_MEMORY_HOTPLUG |
3947be196 [PATCH] memory ho... |
156 |
|
ec69acbb1 [PATCH] hot-add-m... |
157 158 159 |
config MEMORY_HOTPLUG_SPARSE def_bool y depends on SPARSEMEM && MEMORY_HOTPLUG |
8604d9e53 memory_hotplug: i... |
160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 |
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. |
0c0e61958 memory unplug: pa... |
175 176 |
config MEMORY_HOTREMOVE bool "Allow for memory hot remove" |
46723bfa5 memory-hotplug: i... |
177 |
select MEMORY_ISOLATION |
f7e3334a6 powerpc: Fix memo... |
178 |
select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64) |
0c0e61958 memory unplug: pa... |
179 180 |
depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE depends on MIGRATION |
4c21e2f24 [PATCH] mm: split... |
181 182 183 184 185 |
# 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 [PATCH] mm: updat... |
186 |
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes. |
a70caa8ba mm: stop ptlock e... |
187 |
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page. |
4c21e2f24 [PATCH] mm: split... |
188 189 190 |
# config SPLIT_PTLOCK_CPUS int |
9164550ec mm: disable split... |
191 |
default "999999" if !MMU |
a70caa8ba mm: stop ptlock e... |
192 193 |
default "999999" if ARM && !CPU_CACHE_VIPT default "999999" if PARISC && !PA20 |
4c21e2f24 [PATCH] mm: split... |
194 |
default "4" |
7cbe34cf8 [PATCH] Swap Migr... |
195 |
|
e009bb30c mm: implement spl... |
196 |
config ARCH_ENABLE_SPLIT_PMD_PTLOCK |
6341e62b2 kconfig: use bool... |
197 |
bool |
e009bb30c mm: implement spl... |
198 |
|
7cbe34cf8 [PATCH] Swap Migr... |
199 |
# |
09316c09d mm/balloon_compac... |
200 201 |
# support for memory balloon config MEMORY_BALLOON |
6341e62b2 kconfig: use bool... |
202 |
bool |
09316c09d mm/balloon_compac... |
203 204 |
# |
18468d93e mm: introduce a c... |
205 206 207 208 |
# support for memory balloon compaction config BALLOON_COMPACTION bool "Allow for balloon memory compaction/migration" def_bool y |
09316c09d mm/balloon_compac... |
209 |
depends on COMPACTION && MEMORY_BALLOON |
18468d93e mm: introduce a c... |
210 211 212 213 214 215 216 217 218 219 |
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. # |
e9e96b39f mm: allow CONFIG_... |
220 221 222 |
# support for memory compaction config COMPACTION bool "Allow for memory compaction" |
05106e6a5 mm: enable CONFIG... |
223 |
def_bool y |
e9e96b39f mm: allow CONFIG_... |
224 |
select MIGRATION |
33a938774 mm: compaction: d... |
225 |
depends on MMU |
e9e96b39f mm: allow CONFIG_... |
226 |
help |
b32eaf71d mm: clarify COMPA... |
227 228 229 230 231 232 233 234 |
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. |
e9e96b39f mm: allow CONFIG_... |
235 236 |
# |
7cbe34cf8 [PATCH] Swap Migr... |
237 238 239 |
# support for page migration # config MIGRATION |
b20a35035 [PATCH] page migr... |
240 |
bool "Page migration" |
6c5240ae7 [PATCH] Swapless ... |
241 |
def_bool y |
de32a8177 mm/Kconfig: add M... |
242 |
depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU |
b20a35035 [PATCH] page migr... |
243 244 |
help Allows the migration of the physical location of pages of processes |
e9e96b39f mm: allow CONFIG_... |
245 246 247 248 249 |
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 [PATCH] 64bit Res... |
250 |
|
c177c81e0 hugetlb: restrict... |
251 |
config ARCH_ENABLE_HUGEPAGE_MIGRATION |
6341e62b2 kconfig: use bool... |
252 |
bool |
c177c81e0 hugetlb: restrict... |
253 |
|
9c670ea37 mm: thp: introduc... |
254 255 |
config ARCH_ENABLE_THP_MIGRATION bool |
600715dcd generic: add phys... |
256 257 |
config PHYS_ADDR_T_64BIT def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT |
2a7326b5b CONFIG_BOUNCE to ... |
258 |
config BOUNCE |
9ca24e2e1 mmKconfig: add an... |
259 260 |
bool "Enable bounce buffers" default y |
2a7326b5b CONFIG_BOUNCE to ... |
261 |
depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM) |
9ca24e2e1 mmKconfig: add an... |
262 263 264 265 266 |
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. |
2a7326b5b CONFIG_BOUNCE to ... |
267 |
|
ffecfd1a7 block: optionally... |
268 269 270 |
# 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. |
ffecfd1a7 block: optionally... |
271 272 |
config NEED_BOUNCE_POOL bool |
debeb2979 mm/Kconfig: NEED_... |
273 |
default y if TILE && USB_OHCI_HCD |
ffecfd1a7 block: optionally... |
274 |
|
6225e9373 Quicklists for pa... |
275 276 277 278 |
config NR_QUICK int depends on QUICKLIST default "1" |
f057eac0d Introduce CONFIG_... |
279 280 |
config VIRT_TO_BUS |
4febd95a8 Select VIRT_TO_BU... |
281 282 283 284 285 |
bool help An architecture should select this if it implements the deprecated interface virt_to_bus(). All new architectures should probably not select this. |
cddb8a5c1 mmu-notifiers: core |
286 287 288 |
config MMU_NOTIFIER bool |
83fe27ea5 rcu: Make SRCU op... |
289 |
select SRCU |
fc4d5c292 nommu: make the i... |
290 |
|
f8af4da3b ksm: the mm inter... |
291 292 293 294 295 296 297 |
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 ksm: remove unswa... |
298 |
the many instances by a single page with that content, so |
f8af4da3b ksm: the mm inter... |
299 300 |
saving memory until one or another app needs to modify the content. Recommended for use with KVM, or with other duplicative applications. |
c73602ad3 ksm: more on defa... |
301 302 303 |
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 ksm: the mm inter... |
304 |
|
e0a94c2a6 security: use mma... |
305 306 |
config DEFAULT_MMAP_MIN_ADDR int "Low address space to protect from user allocation" |
6e1415467 NOMMU: Optimise a... |
307 |
depends on MMU |
e0a94c2a6 security: use mma... |
308 309 310 311 312 313 314 315 316 |
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 Security/SELinux:... |
317 318 319 |
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 security: use mma... |
320 321 322 |
This value can be changed after boot using the /proc/sys/vm/mmap_min_addr tunable. |
d949f36f1 x86: Fix hwpoison... |
323 324 |
config ARCH_SUPPORTS_MEMORY_FAILURE bool |
e0a94c2a6 security: use mma... |
325 |
|
6a46079cf HWPOISON: The hig... |
326 327 |
config MEMORY_FAILURE depends on MMU |
d949f36f1 x86: Fix hwpoison... |
328 |
depends on ARCH_SUPPORTS_MEMORY_FAILURE |
6a46079cf HWPOISON: The hig... |
329 |
bool "Enable recovery from hardware memory errors" |
ee6f509c3 mm: factor out me... |
330 |
select MEMORY_ISOLATION |
97f0b1345 tracing: add trac... |
331 |
select RAS |
6a46079cf HWPOISON: The hig... |
332 333 334 335 336 |
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 HWPOISON: Add sim... |
337 |
config HWPOISON_INJECT |
413f9efbc HWPOISON: mention... |
338 |
tristate "HWPoison pages injector" |
27df5068e HWPOISON: Add PRO... |
339 |
depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS |
478c5ffc0 HWPOISON: add pag... |
340 |
select PROC_PAGE_MONITOR |
cae681fc1 HWPOISON: Add sim... |
341 |
|
fc4d5c292 nommu: make the i... |
342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 |
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 percpu: use percp... |
369 |
|
4c76d9d1f thp: CONFIG_TRANS... |
370 |
config TRANSPARENT_HUGEPAGE |
13ece886d thp: transparent ... |
371 |
bool "Transparent Hugepage Support" |
15626062f thp, x86: introdu... |
372 |
depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE |
5d6892407 thp: select CONFI... |
373 |
select COMPACTION |
57578c2ea raxix-tree: intro... |
374 |
select RADIX_TREE_MULTIORDER |
4c76d9d1f thp: CONFIG_TRANS... |
375 376 377 378 379 380 381 382 383 |
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 thp: transparent ... |
384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 |
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 |
38d8b4e6b mm, THP, swap: de... |
407 408 409 410 411 412 413 414 415 416 417 |
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. |
e496cf3d7 thp: introduce CO... |
418 419 |
config TRANSPARENT_HUGE_PAGECACHE def_bool y |
953c66c2b mm: THP page cach... |
420 |
depends on TRANSPARENT_HUGEPAGE |
e496cf3d7 thp: introduce CO... |
421 422 |
# |
bbddff054 percpu: use percp... |
423 424 425 426 427 428 |
# UP and nommu archs use km based percpu allocator # config NEED_PER_CPU_KM depends on !SMP bool default y |
077b1f83a mm: cleancache co... |
429 430 431 432 433 434 435 436 437 |
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 mm Kconfig typo: ... |
438 |
cleancache code to put the data contained in that page into |
077b1f83a mm: cleancache co... |
439 440 441 442 443 444 445 446 447 448 449 450 451 |
"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 |
27c6aec21 mm: frontswap: co... |
452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 |
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. |
f825c736e mm/cma: Move dma ... |
469 470 471 |
config CMA bool "Contiguous Memory Allocator" |
de32a8177 mm/Kconfig: add M... |
472 |
depends on HAVE_MEMBLOCK && MMU |
f825c736e mm/cma: Move dma ... |
473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 |
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. |
bf550fc93 Merge remote-trac... |
493 |
|
28b24c1fc mm: cma: debugfs ... |
494 495 496 497 498 |
config CMA_DEBUGFS bool "CMA debugfs interface" depends on CMA && DEBUG_FS help Turns on the DebugFS interface for CMA. |
a254129e8 CMA: generalize C... |
499 500 501 502 503 504 505 506 507 508 |
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". |
af8d417a0 mm/zpool: impleme... |
509 510 511 512 |
config MEM_SOFT_DIRTY bool "Track memory changes" depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS select PROC_PAGE_MONITOR |
4e2e2770b zbud: add to mm/ |
513 |
help |
af8d417a0 mm/zpool: impleme... |
514 515 516 517 518 519 |
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. |
4e2e2770b zbud: add to mm/ |
520 |
|
2b2811178 zswap: add to mm/ |
521 522 523 524 |
config ZSWAP bool "Compressed cache for swap pages (EXPERIMENTAL)" depends on FRONTSWAP && CRYPTO=y select CRYPTO_LZO |
12d79d64b mm/zpool: update ... |
525 |
select ZPOOL |
2b2811178 zswap: add to mm/ |
526 527 528 529 530 531 532 533 534 535 536 537 538 539 |
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. |
af8d417a0 mm/zpool: impleme... |
540 541 542 |
config ZPOOL tristate "Common API for compressed memory storage" default n |
0f8975ec4 mm: soft-dirty bi... |
543 |
help |
af8d417a0 mm/zpool: impleme... |
544 545 |
Compressed memory storage API. This allows using either zbud or zsmalloc. |
0f8975ec4 mm: soft-dirty bi... |
546 |
|
af8d417a0 mm/zpool: impleme... |
547 |
config ZBUD |
9a001fc19 z3fold: the 3-fol... |
548 |
tristate "Low (Up to 2x) density storage for compressed pages" |
af8d417a0 mm/zpool: impleme... |
549 550 551 552 553 554 555 |
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. |
bcf1647d0 zsmalloc: move it... |
556 |
|
9a001fc19 z3fold: the 3-fol... |
557 558 559 560 561 562 563 564 565 |
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. |
bcf1647d0 zsmalloc: move it... |
566 |
config ZSMALLOC |
d867f203b mm/zsmalloc: make... |
567 |
tristate "Memory allocator for compressed pages" |
bcf1647d0 zsmalloc: move it... |
568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 |
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. |
2216ee853 mm/Kconfig: fix U... |
587 588 |
You can check speed with zsmalloc benchmark: https://github.com/spartacus06/zsmapbench |
9e5c33d7a mm: create generi... |
589 |
|
0f050d997 mm/zsmalloc: add ... |
590 591 592 593 594 595 596 597 598 |
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. |
9e5c33d7a mm: create generi... |
599 600 |
config GENERIC_EARLY_IOREMAP bool |
042d27acb parisc,metag: Do ... |
601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 |
config MAX_STACK_SIZE_MB int "Maximum user stack size for 32-bit processes (MB)" default 80 range 8 256 if METAG 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 and metag 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. A sane initial value is 80 MB. |
3a80a7fa7 mm: meminit: init... |
616 617 618 619 620 621 |
# For architectures that support deferred memory initialisation config ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT bool config DEFERRED_STRUCT_PAGE_INIT |
1ce221036 mm/Kconfig: corre... |
622 |
bool "Defer initialisation of struct pages to kthreads" |
3a80a7fa7 mm: meminit: init... |
623 624 |
default n depends on ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT |
11e685672 mm: disable DEFER... |
625 |
depends on NO_BOOTMEM && MEMORY_HOTPLUG |
957949243 mm: make CONFIG_D... |
626 |
depends on !FLATMEM |
fc170bda2 mm: don't allow d... |
627 |
depends on !NEED_PER_CPU_KM |
3a80a7fa7 mm: meminit: init... |
628 629 630 631 632 |
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 |
1ce221036 mm/Kconfig: corre... |
633 634 635 636 |
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. |
033fbae98 mm: ZONE_DEVICE f... |
637 |
|
33c3fc71c mm: introduce idl... |
638 639 640 641 642 643 644 645 646 647 648 |
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. See Documentation/vm/idle_page_tracking.txt for more details. |
65f7d0497 mm, x86: Add ARCH... |
649 650 651 |
# arch_add_memory() comprehends device memory config ARCH_HAS_ZONE_DEVICE bool |
033fbae98 mm: ZONE_DEVICE f... |
652 |
config ZONE_DEVICE |
5042db43c mm/ZONE_DEVICE: n... |
653 |
bool "Device memory (pmem, HMM, etc...) hotplug support" |
033fbae98 mm: ZONE_DEVICE f... |
654 655 |
depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE |
99490f16f mm: ZONE_DEVICE d... |
656 |
depends on SPARSEMEM_VMEMMAP |
65f7d0497 mm, x86: Add ARCH... |
657 |
depends on ARCH_HAS_ZONE_DEVICE |
ab1b597ee mm, devm_memremap... |
658 |
select RADIX_TREE_MULTIORDER |
033fbae98 mm: ZONE_DEVICE f... |
659 660 661 662 663 664 665 666 667 |
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. |
06a660ada Merge tag 'media/... |
668 |
|
133ff0eac mm/hmm: heterogen... |
669 670 671 672 673 674 675 676 677 |
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 |
6b368cd4a mm/hmm: avoid blo... |
678 679 |
config MIGRATE_VMA_HELPER bool |
133ff0eac mm/hmm: heterogen... |
680 681 |
config HMM bool |
6b368cd4a mm/hmm: avoid blo... |
682 |
select MIGRATE_VMA_HELPER |
133ff0eac mm/hmm: heterogen... |
683 |
|
c0b124054 mm/hmm/mirror: mi... |
684 685 686 687 688 689 690 691 692 693 694 |
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. |
5042db43c mm/ZONE_DEVICE: n... |
695 696 697 |
config DEVICE_PRIVATE bool "Unaddressable device memory (GPU memory, ...)" depends on ARCH_HAS_HMM |
df6ad6983 mm/device-public-... |
698 |
select HMM |
5042db43c mm/ZONE_DEVICE: n... |
699 700 701 702 703 |
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. |
df6ad6983 mm/device-public-... |
704 705 706 707 708 709 710 711 712 |
config DEVICE_PUBLIC bool "Addressable device memory (like GPU memory)" depends on ARCH_HAS_HMM select HMM help Allows creation of struct pages to represent addressable device memory; i.e., memory that is accessible from both the device and the CPU |
8025e5ddf [media] mm: Provi... |
713 714 |
config FRAME_VECTOR bool |
63c17fb8e mm/core, x86/mm/p... |
715 716 717 |
config ARCH_USES_HIGH_VMA_FLAGS bool |
66d375709 mm/core, x86/mm/p... |
718 719 |
config ARCH_HAS_PKEYS bool |
30a5b5367 percpu: expose st... |
720 721 722 723 724 725 726 727 |
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. |