1 # SPDX-License-Identifier: GPL-2.0-only 1 # SPDX-License-Identifier: GPL-2.0-only
2 2
3 menu "Memory Management options" 3 menu "Memory Management options"
4 4
5 # 5 #
6 # For some reason microblaze and nios2 hard co 6 # For some reason microblaze and nios2 hard code SWAP=n. Hopefully we can
7 # add proper SWAP support to them, in which ca 7 # add proper SWAP support to them, in which case this can be remove.
8 # 8 #
9 config ARCH_NO_SWAP 9 config ARCH_NO_SWAP
10 bool 10 bool
11 11
12 config ZPOOL 12 config ZPOOL
13 bool 13 bool
14 14
15 menuconfig SWAP 15 menuconfig SWAP
16 bool "Support for paging of anonymous 16 bool "Support for paging of anonymous memory (swap)"
17 depends on MMU && BLOCK && !ARCH_NO_SW 17 depends on MMU && BLOCK && !ARCH_NO_SWAP
18 default y 18 default y
19 help 19 help
20 This option allows you to choose whe 20 This option allows you to choose whether you want to have support
21 for so called swap devices or swap f 21 for so called swap devices or swap files in your kernel that are
22 used to provide more virtual memory 22 used to provide more virtual memory than the actual RAM present
23 in your computer. If unsure say Y. 23 in your computer. If unsure say Y.
24 24
25 config ZSWAP 25 config ZSWAP
26 bool "Compressed cache for swap pages" 26 bool "Compressed cache for swap pages"
27 depends on SWAP 27 depends on SWAP
>> 28 select FRONTSWAP
28 select CRYPTO 29 select CRYPTO
29 select ZPOOL 30 select ZPOOL
30 help 31 help
31 A lightweight compressed cache for s 32 A lightweight compressed cache for swap pages. It takes
32 pages that are in the process of bei 33 pages that are in the process of being swapped out and attempts to
33 compress them into a dynamically all 34 compress them into a dynamically allocated RAM-based memory pool.
34 This can result in a significant I/O 35 This can result in a significant I/O reduction on swap device and,
35 in the case where decompressing from 36 in the case where decompressing from RAM is faster than swap device
36 reads, can also improve workload per 37 reads, can also improve workload performance.
37 38
38 config ZSWAP_DEFAULT_ON 39 config ZSWAP_DEFAULT_ON
39 bool "Enable the compressed cache for 40 bool "Enable the compressed cache for swap pages by default"
40 depends on ZSWAP 41 depends on ZSWAP
41 help 42 help
42 If selected, the compressed cache fo 43 If selected, the compressed cache for swap pages will be enabled
43 at boot, otherwise it will be disabl 44 at boot, otherwise it will be disabled.
44 45
45 The selection made here can be overr 46 The selection made here can be overridden by using the kernel
46 command line 'zswap.enabled=' option 47 command line 'zswap.enabled=' option.
47 48
48 config ZSWAP_SHRINKER_DEFAULT_ON <<
49 bool "Shrink the zswap pool on memory <<
50 depends on ZSWAP <<
51 default n <<
52 help <<
53 If selected, the zswap shrinker will <<
54 stored in the zswap pool will become <<
55 written back to the backing swap dev <<
56 <<
57 This means that zswap writeback coul <<
58 not yet full, or the cgroup zswap li <<
59 reducing the chance that cold pages <<
60 and consume memory indefinitely. <<
61 <<
62 choice 49 choice
63 prompt "Default compressor" 50 prompt "Default compressor"
64 depends on ZSWAP 51 depends on ZSWAP
65 default ZSWAP_COMPRESSOR_DEFAULT_LZO 52 default ZSWAP_COMPRESSOR_DEFAULT_LZO
66 help 53 help
67 Selects the default compression algo 54 Selects the default compression algorithm for the compressed cache
68 for swap pages. 55 for swap pages.
69 56
70 For an overview what kind of perform 57 For an overview what kind of performance can be expected from
71 a particular compression algorithm p 58 a particular compression algorithm please refer to the benchmarks
72 available at the following LWN page: 59 available at the following LWN page:
73 https://lwn.net/Articles/751795/ 60 https://lwn.net/Articles/751795/
74 61
75 If in doubt, select 'LZO'. 62 If in doubt, select 'LZO'.
76 63
77 The selection made here can be overr 64 The selection made here can be overridden by using the kernel
78 command line 'zswap.compressor=' opt 65 command line 'zswap.compressor=' option.
79 66
80 config ZSWAP_COMPRESSOR_DEFAULT_DEFLATE 67 config ZSWAP_COMPRESSOR_DEFAULT_DEFLATE
81 bool "Deflate" 68 bool "Deflate"
82 select CRYPTO_DEFLATE 69 select CRYPTO_DEFLATE
83 help 70 help
84 Use the Deflate algorithm as the def 71 Use the Deflate algorithm as the default compression algorithm.
85 72
86 config ZSWAP_COMPRESSOR_DEFAULT_LZO 73 config ZSWAP_COMPRESSOR_DEFAULT_LZO
87 bool "LZO" 74 bool "LZO"
88 select CRYPTO_LZO 75 select CRYPTO_LZO
89 help 76 help
90 Use the LZO algorithm as the default 77 Use the LZO algorithm as the default compression algorithm.
91 78
92 config ZSWAP_COMPRESSOR_DEFAULT_842 79 config ZSWAP_COMPRESSOR_DEFAULT_842
93 bool "842" 80 bool "842"
94 select CRYPTO_842 81 select CRYPTO_842
95 help 82 help
96 Use the 842 algorithm as the default 83 Use the 842 algorithm as the default compression algorithm.
97 84
98 config ZSWAP_COMPRESSOR_DEFAULT_LZ4 85 config ZSWAP_COMPRESSOR_DEFAULT_LZ4
99 bool "LZ4" 86 bool "LZ4"
100 select CRYPTO_LZ4 87 select CRYPTO_LZ4
101 help 88 help
102 Use the LZ4 algorithm as the default 89 Use the LZ4 algorithm as the default compression algorithm.
103 90
104 config ZSWAP_COMPRESSOR_DEFAULT_LZ4HC 91 config ZSWAP_COMPRESSOR_DEFAULT_LZ4HC
105 bool "LZ4HC" 92 bool "LZ4HC"
106 select CRYPTO_LZ4HC 93 select CRYPTO_LZ4HC
107 help 94 help
108 Use the LZ4HC algorithm as the defau 95 Use the LZ4HC algorithm as the default compression algorithm.
109 96
110 config ZSWAP_COMPRESSOR_DEFAULT_ZSTD 97 config ZSWAP_COMPRESSOR_DEFAULT_ZSTD
111 bool "zstd" 98 bool "zstd"
112 select CRYPTO_ZSTD 99 select CRYPTO_ZSTD
113 help 100 help
114 Use the zstd algorithm as the defaul 101 Use the zstd algorithm as the default compression algorithm.
115 endchoice 102 endchoice
116 103
117 config ZSWAP_COMPRESSOR_DEFAULT 104 config ZSWAP_COMPRESSOR_DEFAULT
118 string 105 string
119 depends on ZSWAP 106 depends on ZSWAP
120 default "deflate" if ZSWAP_COMPRESSOR_D 107 default "deflate" if ZSWAP_COMPRESSOR_DEFAULT_DEFLATE
121 default "lzo" if ZSWAP_COMPRESSOR_DEFAU 108 default "lzo" if ZSWAP_COMPRESSOR_DEFAULT_LZO
122 default "842" if ZSWAP_COMPRESSOR_DEFAU 109 default "842" if ZSWAP_COMPRESSOR_DEFAULT_842
123 default "lz4" if ZSWAP_COMPRESSOR_DEFAU 110 default "lz4" if ZSWAP_COMPRESSOR_DEFAULT_LZ4
124 default "lz4hc" if ZSWAP_COMPRESSOR_DEF 111 default "lz4hc" if ZSWAP_COMPRESSOR_DEFAULT_LZ4HC
125 default "zstd" if ZSWAP_COMPRESSOR_DEFA 112 default "zstd" if ZSWAP_COMPRESSOR_DEFAULT_ZSTD
126 default "" 113 default ""
127 114
128 choice 115 choice
129 prompt "Default allocator" 116 prompt "Default allocator"
130 depends on ZSWAP 117 depends on ZSWAP
131 default ZSWAP_ZPOOL_DEFAULT_ZSMALLOC i <<
132 default ZSWAP_ZPOOL_DEFAULT_ZBUD 118 default ZSWAP_ZPOOL_DEFAULT_ZBUD
133 help 119 help
134 Selects the default allocator for th 120 Selects the default allocator for the compressed cache for
135 swap pages. 121 swap pages.
136 The default is 'zbud' for compatibil 122 The default is 'zbud' for compatibility, however please do
137 read the description of each of the 123 read the description of each of the allocators below before
138 making a right choice. 124 making a right choice.
139 125
140 The selection made here can be overr 126 The selection made here can be overridden by using the kernel
141 command line 'zswap.zpool=' option. 127 command line 'zswap.zpool=' option.
142 128
143 config ZSWAP_ZPOOL_DEFAULT_ZBUD 129 config ZSWAP_ZPOOL_DEFAULT_ZBUD
144 bool "zbud" 130 bool "zbud"
145 select ZBUD 131 select ZBUD
146 help 132 help
147 Use the zbud allocator as the defaul 133 Use the zbud allocator as the default allocator.
148 134
149 config ZSWAP_ZPOOL_DEFAULT_Z3FOLD_DEPRECATED !! 135 config ZSWAP_ZPOOL_DEFAULT_Z3FOLD
150 bool "z3foldi (DEPRECATED)" !! 136 bool "z3fold"
151 select Z3FOLD_DEPRECATED !! 137 select Z3FOLD
152 help 138 help
153 Use the z3fold allocator as the defa 139 Use the z3fold allocator as the default allocator.
154 140
155 Deprecated and scheduled for removal <<
156 see CONFIG_Z3FOLD_DEPRECATED. <<
157 <<
158 config ZSWAP_ZPOOL_DEFAULT_ZSMALLOC 141 config ZSWAP_ZPOOL_DEFAULT_ZSMALLOC
159 bool "zsmalloc" 142 bool "zsmalloc"
160 select ZSMALLOC 143 select ZSMALLOC
161 help 144 help
162 Use the zsmalloc allocator as the de 145 Use the zsmalloc allocator as the default allocator.
163 endchoice 146 endchoice
164 147
165 config ZSWAP_ZPOOL_DEFAULT 148 config ZSWAP_ZPOOL_DEFAULT
166 string 149 string
167 depends on ZSWAP 150 depends on ZSWAP
168 default "zbud" if ZSWAP_ZPOOL_DEFAULT_Z 151 default "zbud" if ZSWAP_ZPOOL_DEFAULT_ZBUD
169 default "z3fold" if ZSWAP_ZPOOL_DEFAULT !! 152 default "z3fold" if ZSWAP_ZPOOL_DEFAULT_Z3FOLD
170 default "zsmalloc" if ZSWAP_ZPOOL_DEFAU 153 default "zsmalloc" if ZSWAP_ZPOOL_DEFAULT_ZSMALLOC
171 default "" 154 default ""
172 155
173 config ZBUD 156 config ZBUD
174 tristate "2:1 compression allocator (z 157 tristate "2:1 compression allocator (zbud)"
175 depends on ZSWAP 158 depends on ZSWAP
176 help 159 help
177 A special purpose allocator for stor 160 A special purpose allocator for storing compressed pages.
178 It is designed to store up to two co 161 It is designed to store up to two compressed pages per physical
179 page. While this design limits stor 162 page. While this design limits storage density, it has simple and
180 deterministic reclaim properties tha 163 deterministic reclaim properties that make it preferable to a higher
181 density approach when reclaim will b 164 density approach when reclaim will be used.
182 165
183 config Z3FOLD_DEPRECATED !! 166 config Z3FOLD
184 tristate "3:1 compression allocator (z !! 167 tristate "3:1 compression allocator (z3fold)"
185 depends on ZSWAP 168 depends on ZSWAP
186 help 169 help
187 Deprecated and scheduled for removal <<
188 a good reason for using Z3FOLD over <<
189 linux-mm@kvack.org and the zswap mai <<
190 <<
191 A special purpose allocator for stor 170 A special purpose allocator for storing compressed pages.
192 It is designed to store up to three 171 It is designed to store up to three compressed pages per physical
193 page. It is a ZBUD derivative so the 172 page. It is a ZBUD derivative so the simplicity and determinism are
194 still there. 173 still there.
195 174
196 config Z3FOLD <<
197 tristate <<
198 default y if Z3FOLD_DEPRECATED=y <<
199 default m if Z3FOLD_DEPRECATED=m <<
200 depends on Z3FOLD_DEPRECATED <<
201 <<
202 config ZSMALLOC 175 config ZSMALLOC
203 tristate 176 tristate
204 prompt "N:1 compression allocator (zsm !! 177 prompt "N:1 compression allocator (zsmalloc)" if ZSWAP
205 depends on MMU 178 depends on MMU
206 help 179 help
207 zsmalloc is a slab-based memory allo 180 zsmalloc is a slab-based memory allocator designed to store
208 pages of various compression levels 181 pages of various compression levels efficiently. It achieves
209 the highest storage density with the 182 the highest storage density with the least amount of fragmentation.
210 183
211 config ZSMALLOC_STAT 184 config ZSMALLOC_STAT
212 bool "Export zsmalloc statistics" 185 bool "Export zsmalloc statistics"
213 depends on ZSMALLOC 186 depends on ZSMALLOC
214 select DEBUG_FS 187 select DEBUG_FS
215 help 188 help
216 This option enables code in the zsma 189 This option enables code in the zsmalloc to collect various
217 statistics about what's happening in 190 statistics about what's happening in zsmalloc and exports that
218 information to userspace via debugfs 191 information to userspace via debugfs.
219 If unsure, say N. 192 If unsure, say N.
220 193
221 config ZSMALLOC_CHAIN_SIZE 194 config ZSMALLOC_CHAIN_SIZE
222 int "Maximum number of physical pages 195 int "Maximum number of physical pages per-zspage"
223 default 8 196 default 8
224 range 4 16 197 range 4 16
225 depends on ZSMALLOC 198 depends on ZSMALLOC
226 help 199 help
227 This option sets the upper limit on 200 This option sets the upper limit on the number of physical pages
228 that a zmalloc page (zspage) can con 201 that a zmalloc page (zspage) can consist of. The optimal zspage
229 chain size is calculated for each si 202 chain size is calculated for each size class during the
230 initialization of the pool. 203 initialization of the pool.
231 204
232 Changing this option can alter the c 205 Changing this option can alter the characteristics of size classes,
233 such as the number of pages per zspa 206 such as the number of pages per zspage and the number of objects
234 per zspage. This can also result in 207 per zspage. This can also result in different configurations of
235 the pool, as zsmalloc merges size cl 208 the pool, as zsmalloc merges size classes with similar
236 characteristics. 209 characteristics.
237 210
238 For more information, see zsmalloc d 211 For more information, see zsmalloc documentation.
239 212
240 menu "Slab allocator options" !! 213 menu "SLAB allocator options"
>> 214
>> 215 choice
>> 216 prompt "Choose SLAB allocator"
>> 217 default SLUB
>> 218 help
>> 219 This option allows to select a slab allocator.
>> 220
>> 221 config SLAB
>> 222 bool "SLAB"
>> 223 depends on !PREEMPT_RT
>> 224 select HAVE_HARDENED_USERCOPY_ALLOCATOR
>> 225 help
>> 226 The regular slab allocator that is established and known to work
>> 227 well in all environments. It organizes cache hot objects in
>> 228 per cpu and per node queues.
241 229
242 config SLUB 230 config SLUB
243 def_bool y !! 231 bool "SLUB (Unqueued Allocator)"
>> 232 select HAVE_HARDENED_USERCOPY_ALLOCATOR
>> 233 help
>> 234 SLUB is a slab allocator that minimizes cache line usage
>> 235 instead of managing queues of cached objects (SLAB approach).
>> 236 Per cpu caching is realized using slabs of objects instead
>> 237 of queues of objects. SLUB can use memory efficiently
>> 238 and has enhanced diagnostics. SLUB is the default choice for
>> 239 a slab allocator.
244 240
245 config SLUB_TINY !! 241 config SLOB_DEPRECATED
246 bool "Configure for minimal memory foo <<
247 depends on EXPERT 242 depends on EXPERT
>> 243 bool "SLOB (Simple Allocator - DEPRECATED)"
>> 244 depends on !PREEMPT_RT
>> 245 help
>> 246 Deprecated and scheduled for removal in a few cycles. SLUB
>> 247 recommended as replacement. CONFIG_SLUB_TINY can be considered
>> 248 on systems with 16MB or less RAM.
>> 249
>> 250 If you need SLOB to stay, please contact linux-mm@kvack.org and
>> 251 people listed in the SLAB ALLOCATOR section of MAINTAINERS file,
>> 252 with your use case.
>> 253
>> 254 SLOB replaces the stock allocator with a drastically simpler
>> 255 allocator. SLOB is generally more space efficient but
>> 256 does not perform as well on large systems.
>> 257
>> 258 endchoice
>> 259
>> 260 config SLOB
>> 261 bool
>> 262 default y
>> 263 depends on SLOB_DEPRECATED
>> 264
>> 265 config SLUB_TINY
>> 266 bool "Configure SLUB for minimal memory footprint"
>> 267 depends on SLUB && EXPERT
248 select SLAB_MERGE_DEFAULT 268 select SLAB_MERGE_DEFAULT
249 help 269 help
250 Configures the slab allocator in a !! 270 Configures the SLUB allocator in a way to achieve minimal memory
251 footprint, sacrificing scalability, 271 footprint, sacrificing scalability, debugging and other features.
252 This is intended only for the small 272 This is intended only for the smallest system that had used the
253 SLOB allocator and is not recommend 273 SLOB allocator and is not recommended for systems with more than
254 16MB RAM. 274 16MB RAM.
255 275
256 If unsure, say N. 276 If unsure, say N.
257 277
258 config SLAB_MERGE_DEFAULT 278 config SLAB_MERGE_DEFAULT
259 bool "Allow slab caches to be merged" 279 bool "Allow slab caches to be merged"
260 default y 280 default y
>> 281 depends on SLAB || SLUB
261 help 282 help
262 For reduced kernel memory fragmentat 283 For reduced kernel memory fragmentation, slab caches can be
263 merged when they share the same size 284 merged when they share the same size and other characteristics.
264 This carries a risk of kernel heap o 285 This carries a risk of kernel heap overflows being able to
265 overwrite objects from merged caches 286 overwrite objects from merged caches (and more easily control
266 cache layout), which makes such heap 287 cache layout), which makes such heap attacks easier to exploit
267 by attackers. By keeping caches unme 288 by attackers. By keeping caches unmerged, these kinds of exploits
268 can usually only damage objects in t 289 can usually only damage objects in the same cache. To disable
269 merging at runtime, "slab_nomerge" c 290 merging at runtime, "slab_nomerge" can be passed on the kernel
270 command line. 291 command line.
271 292
272 config SLAB_FREELIST_RANDOM 293 config SLAB_FREELIST_RANDOM
273 bool "Randomize slab freelist" 294 bool "Randomize slab freelist"
274 depends on !SLUB_TINY !! 295 depends on SLAB || (SLUB && !SLUB_TINY)
275 help 296 help
276 Randomizes the freelist order used o 297 Randomizes the freelist order used on creating new pages. This
277 security feature reduces the predict 298 security feature reduces the predictability of the kernel slab
278 allocator against heap overflows. 299 allocator against heap overflows.
279 300
280 config SLAB_FREELIST_HARDENED 301 config SLAB_FREELIST_HARDENED
281 bool "Harden slab freelist metadata" 302 bool "Harden slab freelist metadata"
282 depends on !SLUB_TINY !! 303 depends on SLAB || (SLUB && !SLUB_TINY)
283 help 304 help
284 Many kernel heap attacks try to targ 305 Many kernel heap attacks try to target slab cache metadata and
285 other infrastructure. This options m 306 other infrastructure. This options makes minor performance
286 sacrifices to harden the kernel slab 307 sacrifices to harden the kernel slab allocator against common
287 freelist exploit methods. !! 308 freelist exploit methods. Some slab implementations have more
288 !! 309 sanity-checking than others. This option is most effective with
289 config SLAB_BUCKETS !! 310 CONFIG_SLUB.
290 bool "Support allocation from separate <<
291 depends on !SLUB_TINY <<
292 default SLAB_FREELIST_HARDENED <<
293 help <<
294 Kernel heap attacks frequently depen <<
295 specifically-sized allocations with <<
296 that will be allocated into the same <<
297 target object. To avoid sharing thes <<
298 provide an explicitly separated set <<
299 user-controlled allocations. This ma <<
300 memory fragmentation, though in prac <<
301 of extra pages since the bulk of use <<
302 are relatively long-lived. <<
303 <<
304 If unsure, say Y. <<
305 311
306 config SLUB_STATS 312 config SLUB_STATS
307 default n 313 default n
308 bool "Enable performance statistics" !! 314 bool "Enable SLUB performance statistics"
309 depends on SYSFS && !SLUB_TINY !! 315 depends on SLUB && SYSFS && !SLUB_TINY
310 help 316 help
311 The statistics are useful to debug s !! 317 SLUB statistics are useful to debug SLUBs allocation behavior in
312 order find ways to optimize the allo 318 order find ways to optimize the allocator. This should never be
313 enabled for production use since kee 319 enabled for production use since keeping statistics slows down
314 the allocator by a few percentage po 320 the allocator by a few percentage points. The slabinfo command
315 supports the determination of the mo 321 supports the determination of the most active slabs to figure
316 out which slabs are relevant to a pa 322 out which slabs are relevant to a particular load.
317 Try running: slabinfo -DA 323 Try running: slabinfo -DA
318 324
319 config SLUB_CPU_PARTIAL 325 config SLUB_CPU_PARTIAL
320 default y 326 default y
321 depends on SMP && !SLUB_TINY !! 327 depends on SLUB && SMP && !SLUB_TINY
322 bool "Enable per cpu partial caches" !! 328 bool "SLUB per cpu partial cache"
323 help 329 help
324 Per cpu partial caches accelerate ob 330 Per cpu partial caches accelerate objects allocation and freeing
325 that is local to a processor at the 331 that is local to a processor at the price of more indeterminism
326 in the latency of the free. On overf 332 in the latency of the free. On overflow these caches will be cleared
327 which requires the taking of locks t 333 which requires the taking of locks that may cause latency spikes.
328 Typically one would choose no for a 334 Typically one would choose no for a realtime system.
329 335
330 config RANDOM_KMALLOC_CACHES !! 336 endmenu # SLAB allocator options
331 default n <<
332 depends on !SLUB_TINY <<
333 bool "Randomize slab caches for normal <<
334 help <<
335 A hardening feature that creates mul <<
336 normal kmalloc allocation and makes <<
337 on code address, which makes the att <<
338 vulnerable memory objects on the hea <<
339 memory vulnerabilities. <<
340 <<
341 Currently the number of copies is se <<
342 that effectively diverges the memory <<
343 subsystems or modules into different <<
344 limited degree of memory and CPU ove <<
345 system workload. <<
346 <<
347 endmenu # Slab allocator options <<
348 337
349 config SHUFFLE_PAGE_ALLOCATOR 338 config SHUFFLE_PAGE_ALLOCATOR
350 bool "Page allocator randomization" 339 bool "Page allocator randomization"
351 default SLAB_FREELIST_RANDOM && ACPI_N 340 default SLAB_FREELIST_RANDOM && ACPI_NUMA
352 help 341 help
353 Randomization of the page allocator 342 Randomization of the page allocator improves the average
354 utilization of a direct-mapped memor 343 utilization of a direct-mapped memory-side-cache. See section
355 5.2.27 Heterogeneous Memory Attribut 344 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI
356 6.2a specification for an example of 345 6.2a specification for an example of how a platform advertises
357 the presence of a memory-side-cache. 346 the presence of a memory-side-cache. There are also incidental
358 security benefits as it reduces the 347 security benefits as it reduces the predictability of page
359 allocations to compliment SLAB_FREEL 348 allocations to compliment SLAB_FREELIST_RANDOM, but the
360 default granularity of shuffling on !! 349 default granularity of shuffling on the "MAX_ORDER - 1" i.e,
361 order of pages is selected based on !! 350 10th order of pages is selected based on cache utilization
362 on x86. !! 351 benefits on x86.
363 352
364 While the randomization improves cac 353 While the randomization improves cache utilization it may
365 negatively impact workloads on platf 354 negatively impact workloads on platforms without a cache. For
366 this reason, by default, the randomi !! 355 this reason, by default, the randomization is enabled only
367 if SHUFFLE_PAGE_ALLOCATOR=y. The ran !! 356 after runtime detection of a direct-mapped memory-side-cache.
368 with the 'page_alloc.shuffle' kernel !! 357 Otherwise, the randomization may be force enabled with the
>> 358 'page_alloc.shuffle' kernel command line parameter.
369 359
370 Say Y if unsure. 360 Say Y if unsure.
371 361
372 config COMPAT_BRK 362 config COMPAT_BRK
373 bool "Disable heap randomization" 363 bool "Disable heap randomization"
374 default y 364 default y
375 help 365 help
376 Randomizing heap placement makes hea 366 Randomizing heap placement makes heap exploits harder, but it
377 also breaks ancient binaries (includ 367 also breaks ancient binaries (including anything libc5 based).
378 This option changes the bootup defau 368 This option changes the bootup default to heap randomization
379 disabled, and can be overridden at r 369 disabled, and can be overridden at runtime by setting
380 /proc/sys/kernel/randomize_va_space 370 /proc/sys/kernel/randomize_va_space to 2.
381 371
382 On non-ancient distros (post-2000 on 372 On non-ancient distros (post-2000 ones) N is usually a safe choice.
383 373
384 config MMAP_ALLOW_UNINITIALIZED 374 config MMAP_ALLOW_UNINITIALIZED
385 bool "Allow mmapped anonymous memory t 375 bool "Allow mmapped anonymous memory to be uninitialized"
386 depends on EXPERT && !MMU 376 depends on EXPERT && !MMU
387 default n 377 default n
388 help 378 help
389 Normally, and according to the Linux 379 Normally, and according to the Linux spec, anonymous memory obtained
390 from mmap() has its contents cleared 380 from mmap() has its contents cleared before it is passed to
391 userspace. Enabling this config opt 381 userspace. Enabling this config option allows you to request that
392 mmap() skip that if it is given an M 382 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
393 providing a huge performance boost. 383 providing a huge performance boost. If this option is not enabled,
394 then the flag will be ignored. 384 then the flag will be ignored.
395 385
396 This is taken advantage of by uClibc 386 This is taken advantage of by uClibc's malloc(), and also by
397 ELF-FDPIC binfmt's brk and stack all 387 ELF-FDPIC binfmt's brk and stack allocator.
398 388
399 Because of the obvious security issu 389 Because of the obvious security issues, this option should only be
400 enabled on embedded devices where yo 390 enabled on embedded devices where you control what is run in
401 userspace. Since that isn't general 391 userspace. Since that isn't generally a problem on no-MMU systems,
402 it is normally safe to say Y here. 392 it is normally safe to say Y here.
403 393
404 See Documentation/admin-guide/mm/nom 394 See Documentation/admin-guide/mm/nommu-mmap.rst for more information.
405 395
406 config SELECT_MEMORY_MODEL 396 config SELECT_MEMORY_MODEL
407 def_bool y 397 def_bool y
408 depends on ARCH_SELECT_MEMORY_MODEL 398 depends on ARCH_SELECT_MEMORY_MODEL
409 399
410 choice 400 choice
411 prompt "Memory model" 401 prompt "Memory model"
412 depends on SELECT_MEMORY_MODEL 402 depends on SELECT_MEMORY_MODEL
413 default SPARSEMEM_MANUAL if ARCH_SPARS 403 default SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT
414 default FLATMEM_MANUAL 404 default FLATMEM_MANUAL
415 help 405 help
416 This option allows you to change som 406 This option allows you to change some of the ways that
417 Linux manages its memory internally. 407 Linux manages its memory internally. Most users will
418 only have one option here selected b 408 only have one option here selected by the architecture
419 configuration. This is normal. 409 configuration. This is normal.
420 410
421 config FLATMEM_MANUAL 411 config FLATMEM_MANUAL
422 bool "Flat Memory" 412 bool "Flat Memory"
423 depends on !ARCH_SPARSEMEM_ENABLE || A 413 depends on !ARCH_SPARSEMEM_ENABLE || ARCH_FLATMEM_ENABLE
424 help 414 help
425 This option is best suited for non-N 415 This option is best suited for non-NUMA systems with
426 flat address space. The FLATMEM is t 416 flat address space. The FLATMEM is the most efficient
427 system in terms of performance and r 417 system in terms of performance and resource consumption
428 and it is the best option for smalle 418 and it is the best option for smaller systems.
429 419
430 For systems that have holes in their 420 For systems that have holes in their physical address
431 spaces and for features like NUMA an 421 spaces and for features like NUMA and memory hotplug,
432 choose "Sparse Memory". 422 choose "Sparse Memory".
433 423
434 If unsure, choose this option (Flat 424 If unsure, choose this option (Flat Memory) over any other.
435 425
436 config SPARSEMEM_MANUAL 426 config SPARSEMEM_MANUAL
437 bool "Sparse Memory" 427 bool "Sparse Memory"
438 depends on ARCH_SPARSEMEM_ENABLE 428 depends on ARCH_SPARSEMEM_ENABLE
439 help 429 help
440 This will be the only option for som 430 This will be the only option for some systems, including
441 memory hot-plug systems. This is no 431 memory hot-plug systems. This is normal.
442 432
443 This option provides efficient suppo 433 This option provides efficient support for systems with
444 holes is their physical address spac 434 holes is their physical address space and allows memory
445 hot-plug and hot-remove. 435 hot-plug and hot-remove.
446 436
447 If unsure, choose "Flat Memory" over 437 If unsure, choose "Flat Memory" over this option.
448 438
449 endchoice 439 endchoice
450 440
451 config SPARSEMEM 441 config SPARSEMEM
452 def_bool y 442 def_bool y
453 depends on (!SELECT_MEMORY_MODEL && AR 443 depends on (!SELECT_MEMORY_MODEL && ARCH_SPARSEMEM_ENABLE) || SPARSEMEM_MANUAL
454 444
455 config FLATMEM 445 config FLATMEM
456 def_bool y 446 def_bool y
457 depends on !SPARSEMEM || FLATMEM_MANUA 447 depends on !SPARSEMEM || FLATMEM_MANUAL
458 448
459 # 449 #
460 # SPARSEMEM_EXTREME (which is the default) doe 450 # SPARSEMEM_EXTREME (which is the default) does some bootmem
461 # allocations when sparse_init() is called. I 451 # allocations when sparse_init() is called. If this cannot
462 # be done on your architecture, select this op 452 # be done on your architecture, select this option. However,
463 # statically allocating the mem_section[] arra 453 # statically allocating the mem_section[] array can potentially
464 # consume vast quantities of .bss, so be caref 454 # consume vast quantities of .bss, so be careful.
465 # 455 #
466 # This option will also potentially produce sm 456 # This option will also potentially produce smaller runtime code
467 # with gcc 3.4 and later. 457 # with gcc 3.4 and later.
468 # 458 #
469 config SPARSEMEM_STATIC 459 config SPARSEMEM_STATIC
470 bool 460 bool
471 461
472 # 462 #
473 # Architecture platforms which require a two l 463 # Architecture platforms which require a two level mem_section in SPARSEMEM
474 # must select this option. This is usually for 464 # must select this option. This is usually for architecture platforms with
475 # an extremely sparse physical address space. 465 # an extremely sparse physical address space.
476 # 466 #
477 config SPARSEMEM_EXTREME 467 config SPARSEMEM_EXTREME
478 def_bool y 468 def_bool y
479 depends on SPARSEMEM && !SPARSEMEM_STA 469 depends on SPARSEMEM && !SPARSEMEM_STATIC
480 470
481 config SPARSEMEM_VMEMMAP_ENABLE 471 config SPARSEMEM_VMEMMAP_ENABLE
482 bool 472 bool
483 473
484 config SPARSEMEM_VMEMMAP 474 config SPARSEMEM_VMEMMAP
485 bool "Sparse Memory virtual memmap" 475 bool "Sparse Memory virtual memmap"
486 depends on SPARSEMEM && SPARSEMEM_VMEM 476 depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE
487 default y 477 default y
488 help 478 help
489 SPARSEMEM_VMEMMAP uses a virtually m 479 SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise
490 pfn_to_page and page_to_pfn operatio 480 pfn_to_page and page_to_pfn operations. This is the most
491 efficient option when sufficient ker 481 efficient option when sufficient kernel resources are available.
492 # <<
493 # Select this config option from the architect <<
494 # to enable the feature of HugeTLB/dev_dax vme <<
495 # <<
496 config ARCH_WANT_OPTIMIZE_DAX_VMEMMAP <<
497 bool <<
498 <<
499 config ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP <<
500 bool <<
501 482
502 config HAVE_MEMBLOCK_PHYS_MAP 483 config HAVE_MEMBLOCK_PHYS_MAP
503 bool 484 bool
504 485
505 config HAVE_GUP_FAST !! 486 config HAVE_FAST_GUP
506 depends on MMU 487 depends on MMU
507 bool 488 bool
508 489
509 # Don't discard allocated memory used to track 490 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
510 # after early boot, so it can still be used to 491 # after early boot, so it can still be used to test for validity of memory.
511 # Also, memblocks are updated with memory hot( 492 # Also, memblocks are updated with memory hot(un)plug.
512 config ARCH_KEEP_MEMBLOCK 493 config ARCH_KEEP_MEMBLOCK
513 bool 494 bool
514 495
515 # Keep arch NUMA mapping infrastructure post-i 496 # Keep arch NUMA mapping infrastructure post-init.
516 config NUMA_KEEP_MEMINFO 497 config NUMA_KEEP_MEMINFO
517 bool 498 bool
518 499
519 config MEMORY_ISOLATION 500 config MEMORY_ISOLATION
520 bool 501 bool
521 502
522 # IORESOURCE_SYSTEM_RAM regions in the kernel 503 # IORESOURCE_SYSTEM_RAM regions in the kernel resource tree that are marked
523 # IORESOURCE_EXCLUSIVE cannot be mapped to use 504 # IORESOURCE_EXCLUSIVE cannot be mapped to user space, for example, via
524 # /dev/mem. 505 # /dev/mem.
525 config EXCLUSIVE_SYSTEM_RAM 506 config EXCLUSIVE_SYSTEM_RAM
526 def_bool y 507 def_bool y
527 depends on !DEVMEM || STRICT_DEVMEM 508 depends on !DEVMEM || STRICT_DEVMEM
528 509
529 # 510 #
530 # Only be set on architectures that have compl 511 # Only be set on architectures that have completely implemented memory hotplug
531 # feature. If you are not sure, don't touch it 512 # feature. If you are not sure, don't touch it.
532 # 513 #
533 config HAVE_BOOTMEM_INFO_NODE 514 config HAVE_BOOTMEM_INFO_NODE
534 def_bool n 515 def_bool n
535 516
536 config ARCH_ENABLE_MEMORY_HOTPLUG 517 config ARCH_ENABLE_MEMORY_HOTPLUG
537 bool 518 bool
538 519
539 config ARCH_ENABLE_MEMORY_HOTREMOVE 520 config ARCH_ENABLE_MEMORY_HOTREMOVE
540 bool 521 bool
541 522
542 # eventually, we can have this option just 'se 523 # eventually, we can have this option just 'select SPARSEMEM'
543 menuconfig MEMORY_HOTPLUG 524 menuconfig MEMORY_HOTPLUG
544 bool "Memory hotplug" 525 bool "Memory hotplug"
545 select MEMORY_ISOLATION 526 select MEMORY_ISOLATION
546 depends on SPARSEMEM 527 depends on SPARSEMEM
547 depends on ARCH_ENABLE_MEMORY_HOTPLUG 528 depends on ARCH_ENABLE_MEMORY_HOTPLUG
548 depends on 64BIT 529 depends on 64BIT
549 select NUMA_KEEP_MEMINFO if NUMA 530 select NUMA_KEEP_MEMINFO if NUMA
550 531
551 if MEMORY_HOTPLUG 532 if MEMORY_HOTPLUG
552 533
553 config MEMORY_HOTPLUG_DEFAULT_ONLINE 534 config MEMORY_HOTPLUG_DEFAULT_ONLINE
554 bool "Online the newly added memory bl 535 bool "Online the newly added memory blocks by default"
555 depends on MEMORY_HOTPLUG 536 depends on MEMORY_HOTPLUG
556 help 537 help
557 This option sets the default policy 538 This option sets the default policy setting for memory hotplug
558 onlining policy (/sys/devices/system 539 onlining policy (/sys/devices/system/memory/auto_online_blocks) which
559 determines what happens to newly add 540 determines what happens to newly added memory regions. Policy setting
560 can always be changed at runtime. 541 can always be changed at runtime.
561 See Documentation/admin-guide/mm/mem 542 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
562 543
563 Say Y here if you want all hot-plugg 544 Say Y here if you want all hot-plugged memory blocks to appear in
564 'online' state by default. 545 'online' state by default.
565 Say N here if you want the default p 546 Say N here if you want the default policy to keep all hot-plugged
566 memory blocks in 'offline' state. 547 memory blocks in 'offline' state.
567 548
568 config MEMORY_HOTREMOVE 549 config MEMORY_HOTREMOVE
569 bool "Allow for memory hot remove" 550 bool "Allow for memory hot remove"
570 select HAVE_BOOTMEM_INFO_NODE if (X86_ 551 select HAVE_BOOTMEM_INFO_NODE if (X86_64 || PPC64)
571 depends on MEMORY_HOTPLUG && ARCH_ENAB 552 depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE
572 depends on MIGRATION 553 depends on MIGRATION
573 554
574 config MHP_MEMMAP_ON_MEMORY 555 config MHP_MEMMAP_ON_MEMORY
575 def_bool y 556 def_bool y
576 depends on MEMORY_HOTPLUG && SPARSEMEM 557 depends on MEMORY_HOTPLUG && SPARSEMEM_VMEMMAP
577 depends on ARCH_MHP_MEMMAP_ON_MEMORY_E 558 depends on ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
578 559
579 endif # MEMORY_HOTPLUG 560 endif # MEMORY_HOTPLUG
580 561
581 config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE <<
582 bool <<
583 <<
584 # Heavily threaded applications may benefit fr 562 # Heavily threaded applications may benefit from splitting the mm-wide
585 # page_table_lock, so that faults on different 563 # page_table_lock, so that faults on different parts of the user address
586 # space can be handled with less contention: s 564 # space can be handled with less contention: split it at this NR_CPUS.
587 # Default to 4 for wider testing, though 8 mig 565 # Default to 4 for wider testing, though 8 might be more appropriate.
588 # ARM's adjust_pte (unused if VIPT) depends on 566 # ARM's adjust_pte (unused if VIPT) depends on mm-wide page_table_lock.
589 # PA-RISC 7xxx's spinlock_t would enlarge stru 567 # PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
590 # SPARC32 allocates multiple pte tables within 568 # SPARC32 allocates multiple pte tables within a single page, and therefore
591 # a per-page lock leads to problems when multi 569 # a per-page lock leads to problems when multiple tables need to be locked
592 # at the same time (e.g. copy_page_range()). 570 # at the same time (e.g. copy_page_range()).
593 # DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock 571 # DEBUG_SPINLOCK and DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
594 # 572 #
595 config SPLIT_PTE_PTLOCKS !! 573 config SPLIT_PTLOCK_CPUS
596 def_bool y !! 574 int
597 depends on MMU !! 575 default "999999" if !MMU
598 depends on SMP !! 576 default "999999" if ARM && !CPU_CACHE_VIPT
599 depends on NR_CPUS >= 4 !! 577 default "999999" if PARISC && !PA20
600 depends on !ARM || CPU_CACHE_VIPT !! 578 default "999999" if SPARC32
601 depends on !PARISC || PA20 !! 579 default "4"
602 depends on !SPARC32 <<
603 580
604 config ARCH_ENABLE_SPLIT_PMD_PTLOCK 581 config ARCH_ENABLE_SPLIT_PMD_PTLOCK
605 bool 582 bool
606 583
607 config SPLIT_PMD_PTLOCKS <<
608 def_bool y <<
609 depends on SPLIT_PTE_PTLOCKS && ARCH_E <<
610 <<
611 # 584 #
612 # support for memory balloon 585 # support for memory balloon
613 config MEMORY_BALLOON 586 config MEMORY_BALLOON
614 bool 587 bool
615 588
616 # 589 #
617 # support for memory balloon compaction 590 # support for memory balloon compaction
618 config BALLOON_COMPACTION 591 config BALLOON_COMPACTION
619 bool "Allow for balloon memory compact 592 bool "Allow for balloon memory compaction/migration"
620 default y !! 593 def_bool y
621 depends on COMPACTION && MEMORY_BALLOO 594 depends on COMPACTION && MEMORY_BALLOON
622 help 595 help
623 Memory fragmentation introduced by b 596 Memory fragmentation introduced by ballooning might reduce
624 significantly the number of 2MB cont 597 significantly the number of 2MB contiguous memory blocks that can be
625 used within a guest, thus imposing p 598 used within a guest, thus imposing performance penalties associated
626 with the reduced number of transpare 599 with the reduced number of transparent huge pages that could be used
627 by the guest workload. Allowing the 600 by the guest workload. Allowing the compaction & migration for memory
628 pages enlisted as being part of memo 601 pages enlisted as being part of memory balloon devices avoids the
629 scenario aforementioned and helps im 602 scenario aforementioned and helps improving memory defragmentation.
630 603
631 # 604 #
632 # support for memory compaction 605 # support for memory compaction
633 config COMPACTION 606 config COMPACTION
634 bool "Allow for memory compaction" 607 bool "Allow for memory compaction"
635 default y !! 608 def_bool y
636 select MIGRATION 609 select MIGRATION
637 depends on MMU 610 depends on MMU
638 help 611 help
639 Compaction is the only memory manage 612 Compaction is the only memory management component to form
640 high order (larger physically contig 613 high order (larger physically contiguous) memory blocks
641 reliably. The page allocator relies 614 reliably. The page allocator relies on compaction heavily and
642 the lack of the feature can lead to 615 the lack of the feature can lead to unexpected OOM killer
643 invocations for high order memory re 616 invocations for high order memory requests. You shouldn't
644 disable this option unless there rea 617 disable this option unless there really is a strong reason for
645 it and then we would be really inter 618 it and then we would be really interested to hear about that at
646 linux-mm@kvack.org. 619 linux-mm@kvack.org.
647 620
648 config COMPACT_UNEVICTABLE_DEFAULT 621 config COMPACT_UNEVICTABLE_DEFAULT
649 int 622 int
650 depends on COMPACTION 623 depends on COMPACTION
651 default 0 if PREEMPT_RT 624 default 0 if PREEMPT_RT
652 default 1 625 default 1
653 626
654 # 627 #
655 # support for free page reporting 628 # support for free page reporting
656 config PAGE_REPORTING 629 config PAGE_REPORTING
657 bool "Free page reporting" 630 bool "Free page reporting"
>> 631 def_bool n
658 help 632 help
659 Free page reporting allows for the i 633 Free page reporting allows for the incremental acquisition of
660 free pages from the buddy allocator 634 free pages from the buddy allocator for the purpose of reporting
661 those pages to another entity, such 635 those pages to another entity, such as a hypervisor, so that the
662 memory can be freed within the host 636 memory can be freed within the host for other uses.
663 637
664 # 638 #
665 # support for page migration 639 # support for page migration
666 # 640 #
667 config MIGRATION 641 config MIGRATION
668 bool "Page migration" 642 bool "Page migration"
669 default y !! 643 def_bool y
670 depends on (NUMA || ARCH_ENABLE_MEMORY 644 depends on (NUMA || ARCH_ENABLE_MEMORY_HOTREMOVE || COMPACTION || CMA) && MMU
671 help 645 help
672 Allows the migration of the physical 646 Allows the migration of the physical location of pages of processes
673 while the virtual addresses are not 647 while the virtual addresses are not changed. This is useful in
674 two situations. The first is on NUMA 648 two situations. The first is on NUMA systems to put pages nearer
675 to the processors accessing. The sec 649 to the processors accessing. The second is when allocating huge
676 pages as migration can relocate page 650 pages as migration can relocate pages to satisfy a huge page
677 allocation instead of reclaiming. 651 allocation instead of reclaiming.
678 652
679 config DEVICE_MIGRATION 653 config DEVICE_MIGRATION
680 def_bool MIGRATION && ZONE_DEVICE 654 def_bool MIGRATION && ZONE_DEVICE
681 655
682 config ARCH_ENABLE_HUGEPAGE_MIGRATION 656 config ARCH_ENABLE_HUGEPAGE_MIGRATION
683 bool 657 bool
684 658
685 config ARCH_ENABLE_THP_MIGRATION 659 config ARCH_ENABLE_THP_MIGRATION
686 bool 660 bool
687 661
688 config HUGETLB_PAGE_SIZE_VARIABLE 662 config HUGETLB_PAGE_SIZE_VARIABLE
689 def_bool n 663 def_bool n
690 help 664 help
691 Allows the pageblock_order value to 665 Allows the pageblock_order value to be dynamic instead of just standard
692 HUGETLB_PAGE_ORDER when there are mu 666 HUGETLB_PAGE_ORDER when there are multiple HugeTLB page sizes available
693 on a platform. 667 on a platform.
694 668
695 Note that the pageblock_order cannot !! 669 Note that the pageblock_order cannot exceed MAX_ORDER - 1 and will be
696 clamped down to MAX_PAGE_ORDER. !! 670 clamped down to MAX_ORDER - 1.
697 671
698 config CONTIG_ALLOC 672 config CONTIG_ALLOC
699 def_bool (MEMORY_ISOLATION && COMPACTI 673 def_bool (MEMORY_ISOLATION && COMPACTION) || CMA
700 674
701 config PCP_BATCH_SCALE_MAX <<
702 int "Maximum scale factor of PCP (Per- <<
703 default 5 <<
704 range 0 6 <<
705 help <<
706 In page allocator, PCP (Per-CPU page <<
707 batches. The batch number is scaled <<
708 allocation/free throughput. But too <<
709 latency. This option sets the upper <<
710 the maximum latency. <<
711 <<
712 config PHYS_ADDR_T_64BIT 675 config PHYS_ADDR_T_64BIT
713 def_bool 64BIT 676 def_bool 64BIT
714 677
715 config BOUNCE 678 config BOUNCE
716 bool "Enable bounce buffers" 679 bool "Enable bounce buffers"
717 default y 680 default y
718 depends on BLOCK && MMU && HIGHMEM 681 depends on BLOCK && MMU && HIGHMEM
719 help 682 help
720 Enable bounce buffers for devices th 683 Enable bounce buffers for devices that cannot access the full range of
721 memory available to the CPU. Enabled 684 memory available to the CPU. Enabled by default when HIGHMEM is
722 selected, but you may say n to overr 685 selected, but you may say n to override this.
723 686
724 config MMU_NOTIFIER 687 config MMU_NOTIFIER
725 bool 688 bool
>> 689 select SRCU
726 select INTERVAL_TREE 690 select INTERVAL_TREE
727 691
728 config KSM 692 config KSM
729 bool "Enable KSM for page merging" 693 bool "Enable KSM for page merging"
730 depends on MMU 694 depends on MMU
731 select XXHASH 695 select XXHASH
732 help 696 help
733 Enable Kernel Samepage Merging: KSM 697 Enable Kernel Samepage Merging: KSM periodically scans those areas
734 of an application's address space th 698 of an application's address space that an app has advised may be
735 mergeable. When it finds pages of i 699 mergeable. When it finds pages of identical content, it replaces
736 the many instances by a single page 700 the many instances by a single page with that content, so
737 saving memory until one or another a 701 saving memory until one or another app needs to modify the content.
738 Recommended for use with KVM, or wit 702 Recommended for use with KVM, or with other duplicative applications.
739 See Documentation/mm/ksm.rst for mor 703 See Documentation/mm/ksm.rst for more information: KSM is inactive
740 until a program has madvised that an 704 until a program has madvised that an area is MADV_MERGEABLE, and
741 root has set /sys/kernel/mm/ksm/run 705 root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).
742 706
743 config DEFAULT_MMAP_MIN_ADDR 707 config DEFAULT_MMAP_MIN_ADDR
744 int "Low address space to protect from 708 int "Low address space to protect from user allocation"
745 depends on MMU 709 depends on MMU
746 default 4096 710 default 4096
747 help 711 help
748 This is the portion of low virtual m 712 This is the portion of low virtual memory which should be protected
749 from userspace allocation. Keeping 713 from userspace allocation. Keeping a user from writing to low pages
750 can help reduce the impact of kernel 714 can help reduce the impact of kernel NULL pointer bugs.
751 715
752 For most arm64, ppc64 and x86 users !! 716 For most ia64, ppc64 and x86 users with lots of address space
753 a value of 65536 is reasonable and s 717 a value of 65536 is reasonable and should cause no problems.
754 On arm and other archs it should not 718 On arm and other archs it should not be higher than 32768.
755 Programs which use vm86 functionalit 719 Programs which use vm86 functionality or have some need to map
756 this low address space will need CAP 720 this low address space will need CAP_SYS_RAWIO or disable this
757 protection by setting the value to 0 721 protection by setting the value to 0.
758 722
759 This value can be changed after boot 723 This value can be changed after boot using the
760 /proc/sys/vm/mmap_min_addr tunable. 724 /proc/sys/vm/mmap_min_addr tunable.
761 725
762 config ARCH_SUPPORTS_MEMORY_FAILURE 726 config ARCH_SUPPORTS_MEMORY_FAILURE
763 bool 727 bool
764 728
765 config MEMORY_FAILURE 729 config MEMORY_FAILURE
766 depends on MMU 730 depends on MMU
767 depends on ARCH_SUPPORTS_MEMORY_FAILUR 731 depends on ARCH_SUPPORTS_MEMORY_FAILURE
768 bool "Enable recovery from hardware me 732 bool "Enable recovery from hardware memory errors"
769 select MEMORY_ISOLATION 733 select MEMORY_ISOLATION
770 select RAS 734 select RAS
771 help 735 help
772 Enables code to recover from some me 736 Enables code to recover from some memory failures on systems
773 with MCA recovery. This allows a sys 737 with MCA recovery. This allows a system to continue running
774 even when some of its memory has unc 738 even when some of its memory has uncorrected errors. This requires
775 special hardware support and typical 739 special hardware support and typically ECC memory.
776 740
777 config HWPOISON_INJECT 741 config HWPOISON_INJECT
778 tristate "HWPoison pages injector" 742 tristate "HWPoison pages injector"
779 depends on MEMORY_FAILURE && DEBUG_KER 743 depends on MEMORY_FAILURE && DEBUG_KERNEL && PROC_FS
780 select PROC_PAGE_MONITOR 744 select PROC_PAGE_MONITOR
781 745
782 config NOMMU_INITIAL_TRIM_EXCESS 746 config NOMMU_INITIAL_TRIM_EXCESS
783 int "Turn on mmap() excess space trimm 747 int "Turn on mmap() excess space trimming before booting"
784 depends on !MMU 748 depends on !MMU
785 default 1 749 default 1
786 help 750 help
787 The NOMMU mmap() frequently needs to 751 The NOMMU mmap() frequently needs to allocate large contiguous chunks
788 of memory on which to store mappings 752 of memory on which to store mappings, but it can only ask the system
789 allocator for chunks in 2^N*PAGE_SIZ 753 allocator for chunks in 2^N*PAGE_SIZE amounts - which is frequently
790 more than it requires. To deal with 754 more than it requires. To deal with this, mmap() is able to trim off
791 the excess and return it to the allo 755 the excess and return it to the allocator.
792 756
793 If trimming is enabled, the excess i 757 If trimming is enabled, the excess is trimmed off and returned to the
794 system allocator, which can cause ex 758 system allocator, which can cause extra fragmentation, particularly
795 if there are a lot of transient proc 759 if there are a lot of transient processes.
796 760
797 If trimming is disabled, the excess 761 If trimming is disabled, the excess is kept, but not used, which for
798 long-term mappings means that the sp 762 long-term mappings means that the space is wasted.
799 763
800 Trimming can be dynamically controll 764 Trimming can be dynamically controlled through a sysctl option
801 (/proc/sys/vm/nr_trim_pages) which s 765 (/proc/sys/vm/nr_trim_pages) which specifies the minimum number of
802 excess pages there must be before tr 766 excess pages there must be before trimming should occur, or zero if
803 no trimming is to occur. 767 no trimming is to occur.
804 768
805 This option specifies the initial va 769 This option specifies the initial value of this option. The default
806 of 1 says that all excess pages shou 770 of 1 says that all excess pages should be trimmed.
807 771
808 See Documentation/admin-guide/mm/nom 772 See Documentation/admin-guide/mm/nommu-mmap.rst for more information.
809 773
810 config ARCH_WANT_GENERAL_HUGETLB 774 config ARCH_WANT_GENERAL_HUGETLB
811 bool 775 bool
812 776
813 config ARCH_WANTS_THP_SWAP 777 config ARCH_WANTS_THP_SWAP
814 def_bool n 778 def_bool n
815 779
816 menuconfig TRANSPARENT_HUGEPAGE 780 menuconfig TRANSPARENT_HUGEPAGE
817 bool "Transparent Hugepage Support" 781 bool "Transparent Hugepage Support"
818 depends on HAVE_ARCH_TRANSPARENT_HUGEP 782 depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE && !PREEMPT_RT
819 select COMPACTION 783 select COMPACTION
820 select XARRAY_MULTI 784 select XARRAY_MULTI
821 help 785 help
822 Transparent Hugepages allows the ker 786 Transparent Hugepages allows the kernel to use huge pages and
823 huge tlb transparently to the applic 787 huge tlb transparently to the applications whenever possible.
824 This feature can improve computing p 788 This feature can improve computing performance to certain
825 applications by speeding up page fau 789 applications by speeding up page faults during memory
826 allocation, by reducing the number o 790 allocation, by reducing the number of tlb misses and by speeding
827 up the pagetable walking. 791 up the pagetable walking.
828 792
829 If memory constrained on embedded, y 793 If memory constrained on embedded, you may want to say N.
830 794
831 if TRANSPARENT_HUGEPAGE 795 if TRANSPARENT_HUGEPAGE
832 796
833 choice 797 choice
834 prompt "Transparent Hugepage Support s 798 prompt "Transparent Hugepage Support sysfs defaults"
835 depends on TRANSPARENT_HUGEPAGE 799 depends on TRANSPARENT_HUGEPAGE
836 default TRANSPARENT_HUGEPAGE_ALWAYS 800 default TRANSPARENT_HUGEPAGE_ALWAYS
837 help 801 help
838 Selects the sysfs defaults for Trans 802 Selects the sysfs defaults for Transparent Hugepage Support.
839 803
840 config TRANSPARENT_HUGEPAGE_ALWAYS 804 config TRANSPARENT_HUGEPAGE_ALWAYS
841 bool "always" 805 bool "always"
842 help 806 help
843 Enabling Transparent Hugepage always 807 Enabling Transparent Hugepage always, can increase the
844 memory footprint of applications wit 808 memory footprint of applications without a guaranteed
845 benefit but it will work automatical 809 benefit but it will work automatically for all applications.
846 810
847 config TRANSPARENT_HUGEPAGE_MADVISE 811 config TRANSPARENT_HUGEPAGE_MADVISE
848 bool "madvise" 812 bool "madvise"
849 help 813 help
850 Enabling Transparent Hugepage madvis 814 Enabling Transparent Hugepage madvise, will only provide a
851 performance improvement benefit to t 815 performance improvement benefit to the applications using
852 madvise(MADV_HUGEPAGE) but it won't 816 madvise(MADV_HUGEPAGE) but it won't risk to increase the
853 memory footprint of applications wit 817 memory footprint of applications without a guaranteed
854 benefit. 818 benefit.
855 <<
856 config TRANSPARENT_HUGEPAGE_NEVER <<
857 bool "never" <<
858 help <<
859 Disable Transparent Hugepage by defa <<
860 enabled at runtime via sysfs. <<
861 endchoice 819 endchoice
862 820
863 config THP_SWAP 821 config THP_SWAP
864 def_bool y 822 def_bool y
865 depends on TRANSPARENT_HUGEPAGE && ARC 823 depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP && 64BIT
866 help 824 help
867 Swap transparent huge pages in one p 825 Swap transparent huge pages in one piece, without splitting.
868 XXX: For now, swap cluster backing t 826 XXX: For now, swap cluster backing transparent huge page
869 will be split after swapout. 827 will be split after swapout.
870 828
871 For selection by architectures with 829 For selection by architectures with reasonable THP sizes.
872 830
873 config READ_ONLY_THP_FOR_FS 831 config READ_ONLY_THP_FOR_FS
874 bool "Read-only THP for filesystems (E 832 bool "Read-only THP for filesystems (EXPERIMENTAL)"
875 depends on TRANSPARENT_HUGEPAGE && SHM 833 depends on TRANSPARENT_HUGEPAGE && SHMEM
876 834
877 help 835 help
878 Allow khugepaged to put read-only fi 836 Allow khugepaged to put read-only file-backed pages in THP.
879 837
880 This is marked experimental because 838 This is marked experimental because it is a new feature. Write
881 support of file THPs will be develop 839 support of file THPs will be developed in the next few release
882 cycles. 840 cycles.
883 841
884 endif # TRANSPARENT_HUGEPAGE 842 endif # TRANSPARENT_HUGEPAGE
885 843
886 # 844 #
887 # The architecture supports pgtable leaves tha <<
888 # <<
889 config PGTABLE_HAS_HUGE_LEAVES <<
890 def_bool TRANSPARENT_HUGEPAGE || HUGET <<
891 <<
892 # TODO: Allow to be enabled without THP <<
893 config ARCH_SUPPORTS_HUGE_PFNMAP <<
894 def_bool n <<
895 depends on TRANSPARENT_HUGEPAGE <<
896 <<
897 config ARCH_SUPPORTS_PMD_PFNMAP <<
898 def_bool y <<
899 depends on ARCH_SUPPORTS_HUGE_PFNMAP & <<
900 <<
901 config ARCH_SUPPORTS_PUD_PFNMAP <<
902 def_bool y <<
903 depends on ARCH_SUPPORTS_HUGE_PFNMAP & <<
904 <<
905 # <<
906 # UP and nommu archs use km based percpu alloc 845 # UP and nommu archs use km based percpu allocator
907 # 846 #
908 config NEED_PER_CPU_KM 847 config NEED_PER_CPU_KM
909 depends on !SMP || !MMU 848 depends on !SMP || !MMU
910 bool 849 bool
911 default y 850 default y
912 851
913 config NEED_PER_CPU_EMBED_FIRST_CHUNK 852 config NEED_PER_CPU_EMBED_FIRST_CHUNK
914 bool 853 bool
915 854
916 config NEED_PER_CPU_PAGE_FIRST_CHUNK 855 config NEED_PER_CPU_PAGE_FIRST_CHUNK
917 bool 856 bool
918 857
919 config USE_PERCPU_NUMA_NODE_ID 858 config USE_PERCPU_NUMA_NODE_ID
920 bool 859 bool
921 860
922 config HAVE_SETUP_PER_CPU_AREA 861 config HAVE_SETUP_PER_CPU_AREA
923 bool 862 bool
924 863
>> 864 config FRONTSWAP
>> 865 bool
>> 866
925 config CMA 867 config CMA
926 bool "Contiguous Memory Allocator" 868 bool "Contiguous Memory Allocator"
927 depends on MMU 869 depends on MMU
928 select MIGRATION 870 select MIGRATION
929 select MEMORY_ISOLATION 871 select MEMORY_ISOLATION
930 help 872 help
931 This enables the Contiguous Memory A 873 This enables the Contiguous Memory Allocator which allows other
932 subsystems to allocate big physicall 874 subsystems to allocate big physically-contiguous blocks of memory.
933 CMA reserves a region of memory and 875 CMA reserves a region of memory and allows only movable pages to
934 be allocated from it. This way, the 876 be allocated from it. This way, the kernel can use the memory for
935 pagecache and when a subsystem reque 877 pagecache and when a subsystem requests for contiguous area, the
936 allocated pages are migrated away to 878 allocated pages are migrated away to serve the contiguous request.
937 879
938 If unsure, say "n". 880 If unsure, say "n".
939 881
>> 882 config CMA_DEBUG
>> 883 bool "CMA debug messages (DEVELOPMENT)"
>> 884 depends on DEBUG_KERNEL && CMA
>> 885 help
>> 886 Turns on debug messages in CMA. This produces KERN_DEBUG
>> 887 messages for every CMA call as well as various messages while
>> 888 processing calls such as dma_alloc_from_contiguous().
>> 889 This option does not affect warning and error messages.
>> 890
940 config CMA_DEBUGFS 891 config CMA_DEBUGFS
941 bool "CMA debugfs interface" 892 bool "CMA debugfs interface"
942 depends on CMA && DEBUG_FS 893 depends on CMA && DEBUG_FS
943 help 894 help
944 Turns on the DebugFS interface for C 895 Turns on the DebugFS interface for CMA.
945 896
946 config CMA_SYSFS 897 config CMA_SYSFS
947 bool "CMA information through sysfs in 898 bool "CMA information through sysfs interface"
948 depends on CMA && SYSFS 899 depends on CMA && SYSFS
949 help 900 help
950 This option exposes some sysfs attri 901 This option exposes some sysfs attributes to get information
951 from CMA. 902 from CMA.
952 903
953 config CMA_AREAS 904 config CMA_AREAS
954 int "Maximum count of the CMA areas" 905 int "Maximum count of the CMA areas"
955 depends on CMA 906 depends on CMA
956 default 20 if NUMA !! 907 default 19 if NUMA
957 default 8 !! 908 default 7
958 help 909 help
959 CMA allows to create CMA areas for p 910 CMA allows to create CMA areas for particular purpose, mainly,
960 used as device private area. This pa 911 used as device private area. This parameter sets the maximum
961 number of CMA area in the system. 912 number of CMA area in the system.
962 913
963 If unsure, leave the default value " !! 914 If unsure, leave the default value "7" in UMA and "19" in NUMA.
964 915
965 config MEM_SOFT_DIRTY 916 config MEM_SOFT_DIRTY
966 bool "Track memory changes" 917 bool "Track memory changes"
967 depends on CHECKPOINT_RESTORE && HAVE_ 918 depends on CHECKPOINT_RESTORE && HAVE_ARCH_SOFT_DIRTY && PROC_FS
968 select PROC_PAGE_MONITOR 919 select PROC_PAGE_MONITOR
969 help 920 help
970 This option enables memory changes t 921 This option enables memory changes tracking by introducing a
971 soft-dirty bit on pte-s. This bit it 922 soft-dirty bit on pte-s. This bit it set when someone writes
972 into a page just as regular dirty bi 923 into a page just as regular dirty bit, but unlike the latter
973 it can be cleared by hands. 924 it can be cleared by hands.
974 925
975 See Documentation/admin-guide/mm/sof 926 See Documentation/admin-guide/mm/soft-dirty.rst for more details.
976 927
977 config GENERIC_EARLY_IOREMAP 928 config GENERIC_EARLY_IOREMAP
978 bool 929 bool
979 930
980 config STACK_MAX_DEFAULT_SIZE_MB 931 config STACK_MAX_DEFAULT_SIZE_MB
981 int "Default maximum user stack size f 932 int "Default maximum user stack size for 32-bit processes (MB)"
982 default 100 933 default 100
983 range 8 2048 934 range 8 2048
984 depends on STACK_GROWSUP && (!64BIT || 935 depends on STACK_GROWSUP && (!64BIT || COMPAT)
985 help 936 help
986 This is the maximum stack size in Me 937 This is the maximum stack size in Megabytes in the VM layout of 32-bit
987 user processes when the stack grows 938 user processes when the stack grows upwards (currently only on parisc
988 arch) when the RLIMIT_STACK hard lim 939 arch) when the RLIMIT_STACK hard limit is unlimited.
989 940
990 A sane initial value is 100 MB. 941 A sane initial value is 100 MB.
991 942
992 config DEFERRED_STRUCT_PAGE_INIT 943 config DEFERRED_STRUCT_PAGE_INIT
993 bool "Defer initialisation of struct p 944 bool "Defer initialisation of struct pages to kthreads"
994 depends on SPARSEMEM 945 depends on SPARSEMEM
995 depends on !NEED_PER_CPU_KM 946 depends on !NEED_PER_CPU_KM
996 depends on 64BIT 947 depends on 64BIT
997 depends on !KMSAN <<
998 select PADATA 948 select PADATA
999 help 949 help
1000 Ordinarily all struct pages are ini 950 Ordinarily all struct pages are initialised during early boot in a
1001 single thread. On very large machin 951 single thread. On very large machines this can take a considerable
1002 amount of time. If this option is s 952 amount of time. If this option is set, large machines will bring up
1003 a subset of memmap at boot and then 953 a subset of memmap at boot and then initialise the rest in parallel.
1004 This has a potential performance im 954 This has a potential performance impact on tasks running early in the
1005 lifetime of the system until these 955 lifetime of the system until these kthreads finish the
1006 initialisation. 956 initialisation.
1007 957
1008 config PAGE_IDLE_FLAG 958 config PAGE_IDLE_FLAG
1009 bool 959 bool
1010 select PAGE_EXTENSION if !64BIT 960 select PAGE_EXTENSION if !64BIT
1011 help 961 help
1012 This adds PG_idle and PG_young flag 962 This adds PG_idle and PG_young flags to 'struct page'. PTE Accessed
1013 bit writers can set the state of th 963 bit writers can set the state of the bit in the flags so that PTE
1014 Accessed bit readers may avoid dist 964 Accessed bit readers may avoid disturbance.
1015 965
1016 config IDLE_PAGE_TRACKING 966 config IDLE_PAGE_TRACKING
1017 bool "Enable idle page tracking" 967 bool "Enable idle page tracking"
1018 depends on SYSFS && MMU 968 depends on SYSFS && MMU
1019 select PAGE_IDLE_FLAG 969 select PAGE_IDLE_FLAG
1020 help 970 help
1021 This feature allows to estimate the 971 This feature allows to estimate the amount of user pages that have
1022 not been touched during a given per 972 not been touched during a given period of time. This information can
1023 be useful to tune memory cgroup lim 973 be useful to tune memory cgroup limits and/or for job placement
1024 within a compute cluster. 974 within a compute cluster.
1025 975
1026 See Documentation/admin-guide/mm/id 976 See Documentation/admin-guide/mm/idle_page_tracking.rst for
1027 more details. 977 more details.
1028 978
1029 # Architectures which implement cpu_dcache_is <<
1030 # whether the data caches are aliased (VIVT o <<
1031 # aliasing) need to select this. <<
1032 config ARCH_HAS_CPU_CACHE_ALIASING <<
1033 bool <<
1034 <<
1035 config ARCH_HAS_CACHE_LINE_SIZE 979 config ARCH_HAS_CACHE_LINE_SIZE
1036 bool 980 bool
1037 981
1038 config ARCH_HAS_CURRENT_STACK_POINTER 982 config ARCH_HAS_CURRENT_STACK_POINTER
1039 bool 983 bool
1040 help 984 help
1041 In support of HARDENED_USERCOPY per 985 In support of HARDENED_USERCOPY performing stack variable lifetime
1042 checking, an architecture-agnostic 986 checking, an architecture-agnostic way to find the stack pointer
1043 is needed. Once an architecture def 987 is needed. Once an architecture defines an unsigned long global
1044 register alias named "current_stack 988 register alias named "current_stack_pointer", this config can be
1045 selected. 989 selected.
1046 990
1047 config ARCH_HAS_PTE_DEVMAP 991 config ARCH_HAS_PTE_DEVMAP
1048 bool 992 bool
1049 993
1050 config ARCH_HAS_ZONE_DMA_SET 994 config ARCH_HAS_ZONE_DMA_SET
1051 bool 995 bool
1052 996
1053 config ZONE_DMA 997 config ZONE_DMA
1054 bool "Support DMA zone" if ARCH_HAS_Z 998 bool "Support DMA zone" if ARCH_HAS_ZONE_DMA_SET
1055 default y if ARM64 || X86 999 default y if ARM64 || X86
1056 1000
1057 config ZONE_DMA32 1001 config ZONE_DMA32
1058 bool "Support DMA32 zone" if ARCH_HAS 1002 bool "Support DMA32 zone" if ARCH_HAS_ZONE_DMA_SET
1059 depends on !X86_32 1003 depends on !X86_32
1060 default y if ARM64 1004 default y if ARM64
1061 1005
1062 config ZONE_DEVICE 1006 config ZONE_DEVICE
1063 bool "Device memory (pmem, HMM, etc.. 1007 bool "Device memory (pmem, HMM, etc...) hotplug support"
1064 depends on MEMORY_HOTPLUG 1008 depends on MEMORY_HOTPLUG
1065 depends on MEMORY_HOTREMOVE 1009 depends on MEMORY_HOTREMOVE
1066 depends on SPARSEMEM_VMEMMAP 1010 depends on SPARSEMEM_VMEMMAP
1067 depends on ARCH_HAS_PTE_DEVMAP 1011 depends on ARCH_HAS_PTE_DEVMAP
1068 select XARRAY_MULTI 1012 select XARRAY_MULTI
1069 1013
1070 help 1014 help
1071 Device memory hotplug support allow 1015 Device memory hotplug support allows for establishing pmem,
1072 or other device driver discovered m 1016 or other device driver discovered memory regions, in the
1073 memmap. This allows pfn_to_page() l 1017 memmap. This allows pfn_to_page() lookups of otherwise
1074 "device-physical" addresses which i 1018 "device-physical" addresses which is needed for using a DAX
1075 mapping in an O_DIRECT operation, a 1019 mapping in an O_DIRECT operation, among other things.
1076 1020
1077 If FS_DAX is enabled, then say Y. 1021 If FS_DAX is enabled, then say Y.
1078 1022
1079 # 1023 #
1080 # Helpers to mirror range of the CPU page tab 1024 # Helpers to mirror range of the CPU page tables of a process into device page
1081 # tables. 1025 # tables.
1082 # 1026 #
1083 config HMM_MIRROR 1027 config HMM_MIRROR
1084 bool 1028 bool
1085 depends on MMU 1029 depends on MMU
1086 1030
1087 config GET_FREE_REGION 1031 config GET_FREE_REGION
>> 1032 depends on SPARSEMEM
1088 bool 1033 bool
1089 1034
1090 config DEVICE_PRIVATE 1035 config DEVICE_PRIVATE
1091 bool "Unaddressable device memory (GP 1036 bool "Unaddressable device memory (GPU memory, ...)"
1092 depends on ZONE_DEVICE 1037 depends on ZONE_DEVICE
1093 select GET_FREE_REGION 1038 select GET_FREE_REGION
1094 1039
1095 help 1040 help
1096 Allows creation of struct pages to 1041 Allows creation of struct pages to represent unaddressable device
1097 memory; i.e., memory that is only a 1042 memory; i.e., memory that is only accessible from the device (or
1098 group of devices). You likely also 1043 group of devices). You likely also want to select HMM_MIRROR.
1099 1044
1100 config VMAP_PFN 1045 config VMAP_PFN
1101 bool 1046 bool
1102 1047
1103 config ARCH_USES_HIGH_VMA_FLAGS 1048 config ARCH_USES_HIGH_VMA_FLAGS
1104 bool 1049 bool
1105 config ARCH_HAS_PKEYS 1050 config ARCH_HAS_PKEYS
1106 bool 1051 bool
1107 1052
1108 config ARCH_USES_PG_ARCH_2 !! 1053 config ARCH_USES_PG_ARCH_X
1109 bool <<
1110 config ARCH_USES_PG_ARCH_3 <<
1111 bool 1054 bool
>> 1055 help
>> 1056 Enable the definition of PG_arch_x page flags with x > 1. Only
>> 1057 suitable for 64-bit architectures with CONFIG_FLATMEM or
>> 1058 CONFIG_SPARSEMEM_VMEMMAP enabled, otherwise there may not be
>> 1059 enough room for additional bits in page->flags.
1112 1060
1113 config VM_EVENT_COUNTERS 1061 config VM_EVENT_COUNTERS
1114 default y 1062 default y
1115 bool "Enable VM event counters for /p 1063 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1116 help 1064 help
1117 VM event counters are needed for ev 1065 VM event counters are needed for event counts to be shown.
1118 This option allows the disabling of 1066 This option allows the disabling of the VM event counters
1119 on EXPERT systems. /proc/vmstat wi 1067 on EXPERT systems. /proc/vmstat will only show page counts
1120 if VM event counters are disabled. 1068 if VM event counters are disabled.
1121 1069
1122 config PERCPU_STATS 1070 config PERCPU_STATS
1123 bool "Collect percpu memory statistic 1071 bool "Collect percpu memory statistics"
1124 help 1072 help
1125 This feature collects and exposes s 1073 This feature collects and exposes statistics via debugfs. The
1126 information includes global and per 1074 information includes global and per chunk statistics, which can
1127 be used to help understand percpu m 1075 be used to help understand percpu memory usage.
1128 1076
1129 config GUP_TEST 1077 config GUP_TEST
1130 bool "Enable infrastructure for get_u 1078 bool "Enable infrastructure for get_user_pages()-related unit tests"
1131 depends on DEBUG_FS 1079 depends on DEBUG_FS
1132 help 1080 help
1133 Provides /sys/kernel/debug/gup_test 1081 Provides /sys/kernel/debug/gup_test, which in turn provides a way
1134 to make ioctl calls that can launch 1082 to make ioctl calls that can launch kernel-based unit tests for
1135 the get_user_pages*() and pin_user_ 1083 the get_user_pages*() and pin_user_pages*() family of API calls.
1136 1084
1137 These tests include benchmark testi 1085 These tests include benchmark testing of the _fast variants of
1138 get_user_pages*() and pin_user_page 1086 get_user_pages*() and pin_user_pages*(), as well as smoke tests of
1139 the non-_fast variants. 1087 the non-_fast variants.
1140 1088
1141 There is also a sub-test that allow 1089 There is also a sub-test that allows running dump_page() on any
1142 of up to eight pages (selected by c 1090 of up to eight pages (selected by command line args) within the
1143 range of user-space addresses. Thes 1091 range of user-space addresses. These pages are either pinned via
1144 pin_user_pages*(), or pinned via ge 1092 pin_user_pages*(), or pinned via get_user_pages*(), as specified
1145 by other command line arguments. 1093 by other command line arguments.
1146 1094
1147 See tools/testing/selftests/mm/gup_ 1095 See tools/testing/selftests/mm/gup_test.c
1148 1096
1149 comment "GUP_TEST needs to have DEBUG_FS enab 1097 comment "GUP_TEST needs to have DEBUG_FS enabled"
1150 depends on !GUP_TEST && !DEBUG_FS 1098 depends on !GUP_TEST && !DEBUG_FS
1151 1099
1152 config GUP_GET_PXX_LOW_HIGH 1100 config GUP_GET_PXX_LOW_HIGH
1153 bool 1101 bool
1154 1102
1155 config DMAPOOL_TEST <<
1156 tristate "Enable a module to run time <<
1157 depends on HAS_DMA <<
1158 help <<
1159 Provides a test module that will al <<
1160 various sizes and report how long i <<
1161 provide a consistent way to measure <<
1162 dma_pool_alloc/free routines affect <<
1163 <<
1164 config ARCH_HAS_PTE_SPECIAL 1103 config ARCH_HAS_PTE_SPECIAL
1165 bool 1104 bool
1166 1105
>> 1106 #
>> 1107 # Some architectures require a special hugepage directory format that is
>> 1108 # required to support multiple hugepage sizes. For example a4fe3ce76
>> 1109 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
>> 1110 # introduced it on powerpc. This allows for a more flexible hugepage
>> 1111 # pagetable layouts.
>> 1112 #
>> 1113 config ARCH_HAS_HUGEPD
>> 1114 bool
>> 1115
1167 config MAPPING_DIRTY_HELPERS 1116 config MAPPING_DIRTY_HELPERS
1168 bool 1117 bool
1169 1118
1170 config KMAP_LOCAL 1119 config KMAP_LOCAL
1171 bool 1120 bool
1172 1121
1173 config KMAP_LOCAL_NON_LINEAR_PTE_ARRAY 1122 config KMAP_LOCAL_NON_LINEAR_PTE_ARRAY
1174 bool 1123 bool
1175 1124
1176 # struct io_mapping based helper. Selected b 1125 # struct io_mapping based helper. Selected by drivers that need them
1177 config IO_MAPPING 1126 config IO_MAPPING
1178 bool 1127 bool
1179 1128
1180 config MEMFD_CREATE <<
1181 bool "Enable memfd_create() system ca <<
1182 <<
1183 config SECRETMEM 1129 config SECRETMEM
1184 default y 1130 default y
1185 bool "Enable memfd_secret() system ca 1131 bool "Enable memfd_secret() system call" if EXPERT
1186 depends on ARCH_HAS_SET_DIRECT_MAP 1132 depends on ARCH_HAS_SET_DIRECT_MAP
1187 help 1133 help
1188 Enable the memfd_secret() system ca 1134 Enable the memfd_secret() system call with the ability to create
1189 memory areas visible only in the co 1135 memory areas visible only in the context of the owning process and
1190 not mapped to other processes and o 1136 not mapped to other processes and other kernel page tables.
1191 1137
1192 config ANON_VMA_NAME 1138 config ANON_VMA_NAME
1193 bool "Anonymous VMA name support" 1139 bool "Anonymous VMA name support"
1194 depends on PROC_FS && ADVISE_SYSCALLS 1140 depends on PROC_FS && ADVISE_SYSCALLS && MMU
1195 1141
1196 help 1142 help
1197 Allow naming anonymous virtual memo 1143 Allow naming anonymous virtual memory areas.
1198 1144
1199 This feature allows assigning names 1145 This feature allows assigning names to virtual memory areas. Assigned
1200 names can be later retrieved from / 1146 names can be later retrieved from /proc/pid/maps and /proc/pid/smaps
1201 and help identifying individual ano 1147 and help identifying individual anonymous memory areas.
1202 Assigning a name to anonymous virtu 1148 Assigning a name to anonymous virtual memory area might prevent that
1203 area from being merged with adjacen 1149 area from being merged with adjacent virtual memory areas due to the
1204 difference in their name. 1150 difference in their name.
1205 1151
>> 1152 config USERFAULTFD
>> 1153 bool "Enable userfaultfd() system call"
>> 1154 depends on MMU
>> 1155 help
>> 1156 Enable the userfaultfd() system call that allows to intercept and
>> 1157 handle page faults in userland.
>> 1158
1206 config HAVE_ARCH_USERFAULTFD_WP 1159 config HAVE_ARCH_USERFAULTFD_WP
1207 bool 1160 bool
1208 help 1161 help
1209 Arch has userfaultfd write protecti 1162 Arch has userfaultfd write protection support
1210 1163
1211 config HAVE_ARCH_USERFAULTFD_MINOR 1164 config HAVE_ARCH_USERFAULTFD_MINOR
1212 bool 1165 bool
1213 help 1166 help
1214 Arch has userfaultfd minor fault su 1167 Arch has userfaultfd minor fault support
1215 1168
1216 menuconfig USERFAULTFD <<
1217 bool "Enable userfaultfd() system cal <<
1218 depends on MMU <<
1219 help <<
1220 Enable the userfaultfd() system cal <<
1221 handle page faults in userland. <<
1222 <<
1223 if USERFAULTFD <<
1224 config PTE_MARKER_UFFD_WP 1169 config PTE_MARKER_UFFD_WP
1225 bool "Userfaultfd write protection su 1170 bool "Userfaultfd write protection support for shmem/hugetlbfs"
1226 default y 1171 default y
1227 depends on HAVE_ARCH_USERFAULTFD_WP 1172 depends on HAVE_ARCH_USERFAULTFD_WP
1228 1173
1229 help 1174 help
1230 Allows to create marker PTEs for us 1175 Allows to create marker PTEs for userfaultfd write protection
1231 purposes. It is required to enable 1176 purposes. It is required to enable userfaultfd write protection on
1232 file-backed memory types like shmem 1177 file-backed memory types like shmem and hugetlbfs.
1233 endif # USERFAULTFD <<
1234 1178
1235 # multi-gen LRU { 1179 # multi-gen LRU {
1236 config LRU_GEN 1180 config LRU_GEN
1237 bool "Multi-Gen LRU" 1181 bool "Multi-Gen LRU"
1238 depends on MMU 1182 depends on MMU
1239 # make sure folio->flags has enough s 1183 # make sure folio->flags has enough spare bits
1240 depends on 64BIT || !SPARSEMEM || SPA 1184 depends on 64BIT || !SPARSEMEM || SPARSEMEM_VMEMMAP
1241 help 1185 help
1242 A high performance LRU implementati 1186 A high performance LRU implementation to overcommit memory. See
1243 Documentation/admin-guide/mm/multig 1187 Documentation/admin-guide/mm/multigen_lru.rst for details.
1244 1188
1245 config LRU_GEN_ENABLED 1189 config LRU_GEN_ENABLED
1246 bool "Enable by default" 1190 bool "Enable by default"
1247 depends on LRU_GEN 1191 depends on LRU_GEN
1248 help 1192 help
1249 This option enables the multi-gen L 1193 This option enables the multi-gen LRU by default.
1250 1194
1251 config LRU_GEN_STATS 1195 config LRU_GEN_STATS
1252 bool "Full stats for debugging" 1196 bool "Full stats for debugging"
1253 depends on LRU_GEN 1197 depends on LRU_GEN
1254 help 1198 help
1255 Do not enable this option unless yo 1199 Do not enable this option unless you plan to look at historical stats
1256 from evicted generations for debugg 1200 from evicted generations for debugging purpose.
1257 1201
1258 This option has a per-memcg and per 1202 This option has a per-memcg and per-node memory overhead.
1259 <<
1260 config LRU_GEN_WALKS_MMU <<
1261 def_bool y <<
1262 depends on LRU_GEN && ARCH_HAS_HW_PTE <<
1263 # } 1203 # }
1264 1204
1265 config ARCH_SUPPORTS_PER_VMA_LOCK <<
1266 def_bool n <<
1267 <<
1268 config PER_VMA_LOCK <<
1269 def_bool y <<
1270 depends on ARCH_SUPPORTS_PER_VMA_LOCK <<
1271 help <<
1272 Allow per-vma locking during page f <<
1273 <<
1274 This feature allows locking each vi <<
1275 handling page faults instead of tak <<
1276 <<
1277 config LOCK_MM_AND_FIND_VMA 1205 config LOCK_MM_AND_FIND_VMA
1278 bool 1206 bool
1279 depends on !STACK_GROWSUP 1207 depends on !STACK_GROWSUP
1280 <<
1281 config IOMMU_MM_DATA <<
1282 bool <<
1283 <<
1284 config EXECMEM <<
1285 bool <<
1286 <<
1287 config NUMA_MEMBLKS <<
1288 bool <<
1289 <<
1290 config NUMA_EMU <<
1291 bool "NUMA emulation" <<
1292 depends on NUMA_MEMBLKS <<
1293 help <<
1294 Enable NUMA emulation. A flat machi <<
1295 into virtual nodes when booted with <<
1296 number of nodes. This is only usefu <<
1297 1208
1298 source "mm/damon/Kconfig" 1209 source "mm/damon/Kconfig"
1299 1210
1300 endmenu 1211 endmenu
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.