Blame view
mm/Kconfig
20 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 125 |
config HAVE_MEMBLOCK boolean |
7c0caeb86 memblock: Add opt... |
126 127 |
config HAVE_MEMBLOCK_NODE_MAP boolean |
c378ddd53 memblock, x86: Ma... |
128 129 |
config ARCH_DISCARD_MEMBLOCK boolean |
666167205 memblock: add NO_... |
130 131 |
config NO_BOOTMEM boolean |
ee6f509c3 mm: factor out me... |
132 133 |
config MEMORY_ISOLATION boolean |
20b2f52b7 numa: add CONFIG_... |
134 135 136 137 138 139 |
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 |
c2974058a memory-hotplug: d... |
140 141 142 143 |
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 |
c5320926e mem-hotplug: intr... |
144 145 146 147 148 149 150 151 152 153 154 155 |
memory device cannot be hotplugged. This option allows the following two things: - When the system is booting, node full of hotpluggable memory can be arranged to have only movable memory so that the whole node can be hot-removed. (need movable_node boot option specified). - After the system is up, the option allows users to online all the memory of a node as movable memory so that the whole node can be hot-removed. Users who don't use the memory hotplug feature are fine with this option on since they don't specify movable_node boot option or they don't online memory as movable. |
c2974058a memory-hotplug: d... |
156 157 158 |
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. |
20b2f52b7 numa: add CONFIG_... |
159 |
|
46723bfa5 memory-hotplug: i... |
160 161 162 163 164 165 |
# # 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... |
166 167 168 |
# eventually, we can have this option just 'select SPARSEMEM' config MEMORY_HOTPLUG bool "Allow for memory hot-add" |
ec69acbb1 [PATCH] hot-add-m... |
169 |
depends on SPARSEMEM || X86_64_ACPI_NUMA |
40b313608 Finally eradicate... |
170 |
depends on ARCH_ENABLE_MEMORY_HOTPLUG |
ed84a07a1 powerpc: Limit me... |
171 |
depends on (IA64 || X86 || PPC_BOOK3S_64 || SUPERH || S390) |
3947be196 [PATCH] memory ho... |
172 |
|
ec69acbb1 [PATCH] hot-add-m... |
173 174 175 |
config MEMORY_HOTPLUG_SPARSE def_bool y depends on SPARSEMEM && MEMORY_HOTPLUG |
0c0e61958 memory unplug: pa... |
176 177 |
config MEMORY_HOTREMOVE bool "Allow for memory hot remove" |
46723bfa5 memory-hotplug: i... |
178 |
select MEMORY_ISOLATION |
f7e3334a6 powerpc: Fix memo... |
179 |
select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64) |
0c0e61958 memory unplug: pa... |
180 181 |
depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE depends on MIGRATION |
e20b8cca7 PAGEFLAGS_EXTENDE... |
182 183 184 185 186 187 188 189 190 191 |
# # 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 mm: remove !NUMA ... |
192 |
depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM |
e20b8cca7 PAGEFLAGS_EXTENDE... |
193 |
|
4c21e2f24 [PATCH] mm: split... |
194 195 196 197 198 |
# 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... |
199 |
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes. |
a70caa8ba mm: stop ptlock e... |
200 |
# DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page. |
4c21e2f24 [PATCH] mm: split... |
201 202 203 |
# config SPLIT_PTLOCK_CPUS int |
9164550ec mm: disable split... |
204 |
default "999999" if !MMU |
a70caa8ba mm: stop ptlock e... |
205 206 |
default "999999" if ARM && !CPU_CACHE_VIPT default "999999" if PARISC && !PA20 |
4c21e2f24 [PATCH] mm: split... |
207 |
default "4" |
7cbe34cf8 [PATCH] Swap Migr... |
208 |
|
e009bb30c mm: implement spl... |
209 210 |
config ARCH_ENABLE_SPLIT_PMD_PTLOCK boolean |
7cbe34cf8 [PATCH] Swap Migr... |
211 |
# |
18468d93e mm: introduce a c... |
212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 |
# 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. # |
e9e96b39f mm: allow CONFIG_... |
227 228 229 |
# support for memory compaction config COMPACTION bool "Allow for memory compaction" |
05106e6a5 mm: enable CONFIG... |
230 |
def_bool y |
e9e96b39f mm: allow CONFIG_... |
231 |
select MIGRATION |
33a938774 mm: compaction: d... |
232 |
depends on MMU |
e9e96b39f mm: allow CONFIG_... |
233 234 235 236 |
help Allows the compaction of memory for the allocation of huge pages. # |
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 |
|
600715dcd generic: add phys... |
251 252 |
config PHYS_ADDR_T_64BIT def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT |
4b51d6698 [PATCH] optional ... |
253 254 255 256 |
config ZONE_DMA_FLAG int default "0" if !ZONE_DMA default "1" |
2a7326b5b CONFIG_BOUNCE to ... |
257 |
config BOUNCE |
9ca24e2e1 mmKconfig: add an... |
258 259 |
bool "Enable bounce buffers" default y |
2a7326b5b CONFIG_BOUNCE to ... |
260 |
depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM) |
9ca24e2e1 mmKconfig: add an... |
261 262 263 264 265 |
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 ... |
266 |
|
ffecfd1a7 block: optionally... |
267 268 269 270 271 272 273 274 275 276 277 278 |
# 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) |
6225e9373 Quicklists for pa... |
279 280 281 |
config NR_QUICK int depends on QUICKLIST |
0176bd3da sh: Drop down to ... |
282 |
default "2" if AVR32 |
6225e9373 Quicklists for pa... |
283 |
default "1" |
f057eac0d Introduce CONFIG_... |
284 285 |
config VIRT_TO_BUS |
4febd95a8 Select VIRT_TO_BU... |
286 287 288 289 290 |
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 |
291 292 293 |
config MMU_NOTIFIER bool |
fc4d5c292 nommu: make the i... |
294 |
|
f8af4da3b ksm: the mm inter... |
295 296 297 298 299 300 301 |
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... |
302 |
the many instances by a single page with that content, so |
f8af4da3b ksm: the mm inter... |
303 304 |
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... |
305 306 307 |
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... |
308 |
|
e0a94c2a6 security: use mma... |
309 310 |
config DEFAULT_MMAP_MIN_ADDR int "Low address space to protect from user allocation" |
6e1415467 NOMMU: Optimise a... |
311 |
depends on MMU |
e0a94c2a6 security: use mma... |
312 313 314 315 316 317 318 319 320 |
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:... |
321 322 323 |
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... |
324 325 326 |
This value can be changed after boot using the /proc/sys/vm/mmap_min_addr tunable. |
d949f36f1 x86: Fix hwpoison... |
327 328 |
config ARCH_SUPPORTS_MEMORY_FAILURE bool |
e0a94c2a6 security: use mma... |
329 |
|
6a46079cf HWPOISON: The hig... |
330 331 |
config MEMORY_FAILURE depends on MMU |
d949f36f1 x86: Fix hwpoison... |
332 |
depends on ARCH_SUPPORTS_MEMORY_FAILURE |
6a46079cf HWPOISON: The hig... |
333 |
bool "Enable recovery from hardware memory errors" |
ee6f509c3 mm: factor out me... |
334 |
select MEMORY_ISOLATION |
6a46079cf HWPOISON: The hig... |
335 336 337 338 339 |
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... |
340 |
config HWPOISON_INJECT |
413f9efbc HWPOISON: mention... |
341 |
tristate "HWPoison pages injector" |
27df5068e HWPOISON: Add PRO... |
342 |
depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS |
478c5ffc0 HWPOISON: add pag... |
343 |
select PROC_PAGE_MONITOR |
cae681fc1 HWPOISON: Add sim... |
344 |
|
fc4d5c292 nommu: make the i... |
345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 |
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... |
372 |
|
4c76d9d1f thp: CONFIG_TRANS... |
373 |
config TRANSPARENT_HUGEPAGE |
13ece886d thp: transparent ... |
374 |
bool "Transparent Hugepage Support" |
15626062f thp, x86: introdu... |
375 |
depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE |
5d6892407 thp: select CONFI... |
376 |
select COMPACTION |
4c76d9d1f thp: CONFIG_TRANS... |
377 378 379 380 381 382 383 384 385 |
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 ... |
386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 |
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 |
5febcbe99 Cross Memory Atta... |
409 410 411 412 413 414 415 416 417 |
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. |
bbddff054 percpu: use percp... |
418 419 420 421 422 423 424 |
# # UP and nommu archs use km based percpu allocator # config NEED_PER_CPU_KM depends on !SMP bool default y |
077b1f83a mm: cleancache co... |
425 426 427 428 429 430 431 432 433 |
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: ... |
434 |
cleancache code to put the data contained in that page into |
077b1f83a mm: cleancache co... |
435 436 437 438 439 440 441 442 443 444 445 446 447 |
"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... |
448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 |
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 ... |
465 466 467 |
config CMA bool "Contiguous Memory Allocator" |
de32a8177 mm/Kconfig: add M... |
468 |
depends on HAVE_MEMBLOCK && MMU |
f825c736e mm/cma: Move dma ... |
469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 |
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... |
489 |
|
4e2e2770b zbud: add to mm/ |
490 491 492 493 494 495 496 497 498 |
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. |
2b2811178 zswap: add to mm/ |
499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 |
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. |
0f8975ec4 mm: soft-dirty bi... |
518 519 |
config MEM_SOFT_DIRTY bool "Track memory changes" |
a844f3867 mm: add missing d... |
520 |
depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS |
0f8975ec4 mm: soft-dirty bi... |
521 522 523 524 525 526 527 528 |
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. |
bcf1647d0 zsmalloc: move it... |
529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 |
config ZSMALLOC bool "Memory allocator for compressed pages" 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... |
551 552 |
You can check speed with zsmalloc benchmark: https://github.com/spartacus06/zsmapbench |
9e5c33d7a mm: create generi... |
553 554 555 |
config GENERIC_EARLY_IOREMAP bool |