Skip to content

Commit eb0ece1

Browse files
committed
Merge tag 'mm-stable-2025-03-30-16-52' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Pull MM updates from Andrew Morton: - The series "Enable strict percpu address space checks" from Uros Bizjak uses x86 named address space qualifiers to provide compile-time checking of percpu area accesses. This has caused a small amount of fallout - two or three issues were reported. In all cases the calling code was found to be incorrect. - The series "Some cleanup for memcg" from Chen Ridong implements some relatively monir cleanups for the memcontrol code. - The series "mm: fixes for device-exclusive entries (hmm)" from David Hildenbrand fixes a boatload of issues which David found then using device-exclusive PTE entries when THP is enabled. More work is needed, but this makes thins better - our own HMM selftests now succeed. - The series "mm: zswap: remove z3fold and zbud" from Yosry Ahmed remove the z3fold and zbud implementations. They have been deprecated for half a year and nobody has complained. - The series "mm: further simplify VMA merge operation" from Lorenzo Stoakes implements numerous simplifications in this area. No runtime effects are anticipated. - The series "mm/madvise: remove redundant mmap_lock operations from process_madvise()" from SeongJae Park rationalizes the locking in the madvise() implementation. Performance gains of 20-25% were observed in one MADV_DONTNEED microbenchmark. - The series "Tiny cleanup and improvements about SWAP code" from Baoquan He contains a number of touchups to issues which Baoquan noticed when working on the swap code. - The series "mm: kmemleak: Usability improvements" from Catalin Marinas implements a couple of improvements to the kmemleak user-visible output. - The series "mm/damon/paddr: fix large folios access and schemes handling" from Usama Arif provides a couple of fixes for DAMON's handling of large folios. - The series "mm/damon/core: fix wrong and/or useless damos_walk() behaviors" from SeongJae Park fixes a few issues with the accuracy of kdamond's walking of DAMON regions. - The series "expose mapping wrprotect, fix fb_defio use" from Lorenzo Stoakes changes the interaction between framebuffer deferred-io and core MM. No functional changes are anticipated - this is preparatory work for the future removal of page structure fields. - The series "mm/damon: add support for hugepage_size DAMOS filter" from Usama Arif adds a DAMOS filter which permits the filtering by huge page sizes. - The series "mm: permit guard regions for file-backed/shmem mappings" from Lorenzo Stoakes extends the guard region feature from its present "anon mappings only" state. The feature now covers shmem and file-backed mappings. - The series "mm: batched unmap lazyfree large folios during reclamation" from Barry Song cleans up and speeds up the unmapping for pte-mapped large folios. - The series "reimplement per-vma lock as a refcount" from Suren Baghdasaryan puts the vm_lock back into the vma. Our reasons for pulling it out were largely bogus and that change made the code more messy. This patchset provides small (0-10%) improvements on one microbenchmark. - The series "Docs/mm/damon: misc DAMOS filters documentation fixes and improves" from SeongJae Park does some maintenance work on the DAMON docs. - The series "hugetlb/CMA improvements for large systems" from Frank van der Linden addresses a pile of issues which have been observed when using CMA on large machines. - The series "mm/damon: introduce DAMOS filter type for unmapped pages" from SeongJae Park enables users of DMAON/DAMOS to filter my the page's mapped/unmapped status. - The series "zsmalloc/zram: there be preemption" from Sergey Senozhatsky teaches zram to run its compression and decompression operations preemptibly. - The series "selftests/mm: Some cleanups from trying to run them" from Brendan Jackman fixes a pile of unrelated issues which Brendan encountered while runnimg our selftests. - The series "fs/proc/task_mmu: add guard region bit to pagemap" from Lorenzo Stoakes permits userspace to use /proc/pid/pagemap to determine whether a particular page is a guard page. - The series "mm, swap: remove swap slot cache" from Kairui Song removes the swap slot cache from the allocation path - it simply wasn't being effective. - The series "mm: cleanups for device-exclusive entries (hmm)" from David Hildenbrand implements a number of unrelated cleanups in this code. - The series "mm: Rework generic PTDUMP configs" from Anshuman Khandual implements a number of preparatoty cleanups to the GENERIC_PTDUMP Kconfig logic. - The series "mm/damon: auto-tune aggregation interval" from SeongJae Park implements a feedback-driven automatic tuning feature for DAMON's aggregation interval tuning. - The series "Fix lazy mmu mode" from Ryan Roberts fixes some issues in powerpc, sparc and x86 lazy MMU implementations. Ryan did this in preparation for implementing lazy mmu mode for arm64 to optimize vmalloc. - The series "mm/page_alloc: Some clarifications for migratetype fallback" from Brendan Jackman reworks some commentary to make the code easier to follow. - The series "page_counter cleanup and size reduction" from Shakeel Butt cleans up the page_counter code and fixes a size increase which we accidentally added late last year. - The series "Add a command line option that enables control of how many threads should be used to allocate huge pages" from Thomas Prescher does that. It allows the careful operator to significantly reduce boot time by tuning the parallalization of huge page initialization. - The series "Fix calculations in trace_balance_dirty_pages() for cgwb" from Tang Yizhou fixes the tracing output from the dirty page balancing code. - The series "mm/damon: make allow filters after reject filters useful and intuitive" from SeongJae Park improves the handling of allow and reject filters. Behaviour is made more consistent and the documention is updated accordingly. - The series "Switch zswap to object read/write APIs" from Yosry Ahmed updates zswap to the new object read/write APIs and thus permits the removal of some legacy code from zpool and zsmalloc. - The series "Some trivial cleanups for shmem" from Baolin Wang does as it claims. - The series "fs/dax: Fix ZONE_DEVICE page reference counts" from Alistair Popple regularizes the weird ZONE_DEVICE page refcount handling in DAX, permittig the removal of a number of special-case checks. - The series "refactor mremap and fix bug" from Lorenzo Stoakes is a preparatoty refactoring and cleanup of the mremap() code. - The series "mm: MM owner tracking for large folios (!hugetlb) + CONFIG_NO_PAGE_MAPCOUNT" from David Hildenbrand reworks the manner in which we determine whether a large folio is known to be mapped exclusively into a single MM. - The series "mm/damon: add sysfs dirs for managing DAMOS filters based on handling layers" from SeongJae Park adds a couple of new sysfs directories to ease the management of DAMON/DAMOS filters. - The series "arch, mm: reduce code duplication in mem_init()" from Mike Rapoport consolidates many per-arch implementations of mem_init() into code generic code, where that is practical. - The series "mm/damon/sysfs: commit parameters online via damon_call()" from SeongJae Park continues the cleaning up of sysfs access to DAMON internal data. - The series "mm: page_ext: Introduce new iteration API" from Luiz Capitulino reworks the page_ext initialization to fix a boot-time crash which was observed with an unusual combination of compile and cmdline options. - The series "Buddy allocator like (or non-uniform) folio split" from Zi Yan reworks the code to split a folio into smaller folios. The main benefit is lessened memory consumption: fewer post-split folios are generated. - The series "Minimize xa_node allocation during xarry split" from Zi Yan reduces the number of xarray xa_nodes which are generated during an xarray split. - The series "drivers/base/memory: Two cleanups" from Gavin Shan performs some maintenance work on the drivers/base/memory code. - The series "Add tracepoints for lowmem reserves, watermarks and totalreserve_pages" from Martin Liu adds some more tracepoints to the page allocator code. - The series "mm/madvise: cleanup requests validations and classifications" from SeongJae Park cleans up some warts which SeongJae observed during his earlier madvise work. - The series "mm/hwpoison: Fix regressions in memory failure handling" from Shuai Xue addresses two quite serious regressions which Shuai has observed in the memory-failure implementation. - The series "mm: reliable huge page allocator" from Johannes Weiner makes huge page allocations cheaper and more reliable by reducing fragmentation. - The series "Minor memcg cleanups & prep for memdescs" from Matthew Wilcox is preparatory work for the future implementation of memdescs. - The series "track memory used by balloon drivers" from Nico Pache introduces a way to track memory used by our various balloon drivers. - The series "mm/damon: introduce DAMOS filter type for active pages" from Nhat Pham permits users to filter for active/inactive pages, separately for file and anon pages. - The series "Adding Proactive Memory Reclaim Statistics" from Hao Jia separates the proactive reclaim statistics from the direct reclaim statistics. - The series "mm/vmscan: don't try to reclaim hwpoison folio" from Jinjiang Tu fixes our handling of hwpoisoned pages within the reclaim code. * tag 'mm-stable-2025-03-30-16-52' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (431 commits) mm/page_alloc: remove unnecessary __maybe_unused in order_to_pindex() x86/mm: restore early initialization of high_memory for 32-bits mm/vmscan: don't try to reclaim hwpoison folio mm/hwpoison: introduce folio_contain_hwpoisoned_page() helper cgroup: docs: add pswpin and pswpout items in cgroup v2 doc mm: vmscan: split proactive reclaim statistics from direct reclaim statistics selftests/mm: speed up split_huge_page_test selftests/mm: uffd-unit-tests support for hugepages > 2M docs/mm/damon/design: document active DAMOS filter type mm/damon: implement a new DAMOS filter type for active pages fs/dax: don't disassociate zero page entries MM documentation: add "Unaccepted" meminfo entry selftests/mm: add commentary about 9pfs bugs fork: use __vmalloc_node() for stack allocation docs/mm: Physical Memory: Populate the "Zones" section xen: balloon: update the NR_BALLOON_PAGES state hv_balloon: update the NR_BALLOON_PAGES state balloon_compaction: update the NR_BALLOON_PAGES state meminfo: add a per node counter for balloon drivers mm: remove references to folio in __memcg_kmem_uncharge_page() ...
2 parents 0873308 + 0a1e082 commit eb0ece1

File tree

355 files changed

+12721
-8831
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

355 files changed

+12721
-8831
lines changed

CREDITS

+3
Original file line numberDiff line numberDiff line change
@@ -1895,6 +1895,7 @@ S: Czech Republic
18951895
N: Seth Jennings
18961896
18971897
D: Creation and maintenance of zswap
1898+
D: Creation and maintenace of the zbud allocator
18981899

18991900
N: Jeremy Kerr
19001901
D: Maintainer of SPU File System
@@ -3803,6 +3804,7 @@ N: Dan Streetman
38033804
38043805
D: Maintenance and development of zswap
38053806
D: Creation and maintenance of the zpool API
3807+
D: Maintenace of the zbud allocator
38063808

38073809
N: Drew Sullivan
38083810
@@ -4330,6 +4332,7 @@ S: England
43304332
N: Vitaly Wool
43314333
43324334
D: Maintenance and development of zswap
4335+
D: Maintenance and development of z3fold
43334336

43344337
N: Chris Wright
43354338

Documentation/ABI/testing/sysfs-block-zram

-8
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,6 @@ Description:
2222
device. The reset operation frees all the memory associated
2323
with this device.
2424

25-
What: /sys/block/zram<id>/max_comp_streams
26-
Date: February 2014
27-
Contact: Sergey Senozhatsky <[email protected]>
28-
Description:
29-
The max_comp_streams file is read-write and specifies the
30-
number of backend's zcomp_strm compression streams (number of
31-
concurrent compress operations).
32-
3325
What: /sys/block/zram<id>/comp_algorithm
3426
Date: February 2014
3527
Contact: Sergey Senozhatsky <[email protected]>

Documentation/ABI/testing/sysfs-kernel-mm-cma

+13
Original file line numberDiff line numberDiff line change
@@ -29,3 +29,16 @@ Date: Feb 2024
2929
Contact: Anshuman Khandual <[email protected]>
3030
Description:
3131
the number of pages CMA API succeeded to release
32+
33+
What: /sys/kernel/mm/cma/<cma-heap-name>/total_pages
34+
Date: Jun 2024
35+
Contact: Frank van der Linden <[email protected]>
36+
Description:
37+
The size of the CMA area in pages.
38+
39+
What: /sys/kernel/mm/cma/<cma-heap-name>/available_pages
40+
Date: Jun 2024
41+
Contact: Frank van der Linden <[email protected]>
42+
Description:
43+
The number of pages in the CMA area that are still
44+
available for CMA allocation.

Documentation/ABI/testing/sysfs-kernel-mm-damon

+60
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,36 @@ Description: Writing a value to this file sets the update interval of the
9191
DAMON context in microseconds as the value. Reading this file
9292
returns the value.
9393

94+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/intrvals_goal/access_bp
95+
Date: Feb 2025
96+
Contact: SeongJae Park <[email protected]>
97+
Description: Writing a value to this file sets the monitoring intervals
98+
auto-tuning target DAMON-observed access events ratio within
99+
the given time interval (aggrs in same directory), in bp
100+
(1/10,000). Reading this file returns the value.
101+
102+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/intrvals_goal/aggrs
103+
Date: Feb 2025
104+
Contact: SeongJae Park <[email protected]>
105+
Description: Writing a value to this file sets the time interval to achieve
106+
the monitoring intervals auto-tuning target DAMON-observed
107+
access events ratio (access_bp in same directory) within.
108+
Reading this file returns the value.
109+
110+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/intrvals_goal/min_sample_us
111+
Date: Feb 2025
112+
Contact: SeongJae Park <[email protected]>
113+
Description: Writing a value to this file sets the minimum value of
114+
auto-tuned sampling interval in microseconds. Reading this
115+
file returns the value.
116+
117+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/intrvals_goal/max_sample_us
118+
Date: Feb 2025
119+
Contact: SeongJae Park <[email protected]>
120+
Description: Writing a value to this file sets the maximum value of
121+
auto-tuned sampling interval in microseconds. Reading this
122+
file returns the value.
123+
94124
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/nr_regions/min
95125

96126
WDate: Mar 2022
@@ -345,6 +375,20 @@ Description: If 'addr' is written to the 'type' file, writing to or reading
345375
from this file sets or gets the end address of the address
346376
range for the filter.
347377

378+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/filters/<F>/min
379+
Date: Feb 2025
380+
Contact: SeongJae Park <[email protected]>
381+
Description: If 'hugepage_size' is written to the 'type' file, writing to
382+
or reading from this file sets or gets the minimum size of the
383+
hugepage for the filter.
384+
385+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/filters/<F>/max
386+
Date: Feb 2025
387+
Contact: SeongJae Park <[email protected]>
388+
Description: If 'hugepage_size' is written to the 'type' file, writing to
389+
or reading from this file sets or gets the maximum size of the
390+
hugepage for the filter.
391+
348392
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/filters/<F>/target_idx
349393
Date: Dec 2022
350394
Contact: SeongJae Park <[email protected]>
@@ -365,6 +409,22 @@ Description: Writing 'Y' or 'N' to this file sets whether to allow or reject
365409
applying the scheme's action to the memory that satisfies the
366410
'type' and the 'matching' of the directory.
367411

412+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/core_filters
413+
Date: Feb 2025
414+
Contact: SeongJae Park <[email protected]>
415+
Description: Directory for DAMON core layer-handled DAMOS filters. Files
416+
under this directory works same to those of
417+
/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/filters
418+
directory.
419+
420+
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/ops_filters
421+
Date: Feb 2025
422+
Contact: SeongJae Park <[email protected]>
423+
Description: Directory for DAMON operations set layer-handled DAMOS filters.
424+
Files under this directory works same to those of
425+
/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/filters
426+
directory.
427+
368428
What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/nr_tried
369429
Date: Mar 2022
370430
Contact: SeongJae Park <[email protected]>

Documentation/RCU/whatisRCU.rst

+10
Original file line numberDiff line numberDiff line change
@@ -971,6 +971,16 @@ unfortunately any spinlock in a ``SLAB_TYPESAFE_BY_RCU`` object must be
971971
initialized after each and every call to kmem_cache_alloc(), which renders
972972
reference-free spinlock acquisition completely unsafe. Therefore, when
973973
using ``SLAB_TYPESAFE_BY_RCU``, make proper use of a reference counter.
974+
If using refcount_t, the specialized refcount_{add|inc}_not_zero_acquire()
975+
and refcount_set_release() APIs should be used to ensure correct operation
976+
ordering when verifying object identity and when initializing newly
977+
allocated objects. Acquire fence in refcount_{add|inc}_not_zero_acquire()
978+
ensures that identity checks happen *after* reference count is taken.
979+
refcount_set_release() should be called after a newly allocated object is
980+
fully initialized and release fence ensures that new values are visible
981+
*before* refcount can be successfully taken by other users. Once
982+
refcount_set_release() is called, the object should be considered visible
983+
by other tasks.
974984
(Those willing to initialize their locks in a kmem_cache constructor
975985
may also use locking, including cache-friendly sequence locking.)
976986

Documentation/admin-guide/blockdev/zram.rst

+10-26
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The list of possible return codes:
5454
If you use 'echo', the returned value is set by the 'echo' utility,
5555
and, in general case, something like::
5656

57-
echo 3 > /sys/block/zram0/max_comp_streams
57+
echo foo > /sys/block/zram0/comp_algorithm
5858
if [ $? -ne 0 ]; then
5959
handle_error
6060
fi
@@ -73,21 +73,7 @@ This creates 4 devices: /dev/zram{0,1,2,3}
7373
num_devices parameter is optional and tells zram how many devices should be
7474
pre-created. Default: 1.
7575

76-
2) Set max number of compression streams
77-
========================================
78-
79-
Regardless of the value passed to this attribute, ZRAM will always
80-
allocate multiple compression streams - one per online CPU - thus
81-
allowing several concurrent compression operations. The number of
82-
allocated compression streams goes down when some of the CPUs
83-
become offline. There is no single-compression-stream mode anymore,
84-
unless you are running a UP system or have only 1 CPU online.
85-
86-
To find out how many streams are currently available::
87-
88-
cat /sys/block/zram0/max_comp_streams
89-
90-
3) Select compression algorithm
76+
2) Select compression algorithm
9177
===============================
9278

9379
Using comp_algorithm device attribute one can see available and
@@ -107,7 +93,7 @@ Examples::
10793
For the time being, the `comp_algorithm` content shows only compression
10894
algorithms that are supported by zram.
10995

110-
4) Set compression algorithm parameters: Optional
96+
3) Set compression algorithm parameters: Optional
11197
=================================================
11298

11399
Compression algorithms may support specific parameters which can be
@@ -138,7 +124,7 @@ better the compression ratio, it even can take negatives values for some
138124
algorithms), for other algorithms `level` is acceleration level (the higher
139125
the value the lower the compression ratio).
140126

141-
5) Set Disksize
127+
4) Set Disksize
142128
===============
143129

144130
Set disk size by writing the value to sysfs node 'disksize'.
@@ -158,7 +144,7 @@ There is little point creating a zram of greater than twice the size of memory
158144
since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the
159145
size of the disk when not in use so a huge zram is wasteful.
160146

161-
6) Set memory limit: Optional
147+
5) Set memory limit: Optional
162148
=============================
163149

164150
Set memory limit by writing the value to sysfs node 'mem_limit'.
@@ -177,7 +163,7 @@ Examples::
177163
# To disable memory limit
178164
echo 0 > /sys/block/zram0/mem_limit
179165

180-
7) Activate
166+
6) Activate
181167
===========
182168

183169
::
@@ -188,7 +174,7 @@ Examples::
188174
mkfs.ext4 /dev/zram1
189175
mount /dev/zram1 /tmp
190176

191-
8) Add/remove zram devices
177+
7) Add/remove zram devices
192178
==========================
193179

194180
zram provides a control interface, which enables dynamic (on-demand) device
@@ -208,7 +194,7 @@ execute::
208194

209195
echo X > /sys/class/zram-control/hot_remove
210196

211-
9) Stats
197+
8) Stats
212198
========
213199

214200
Per-device statistics are exported as various nodes under /sys/block/zram<id>/
@@ -228,8 +214,6 @@ mem_limit WO specifies the maximum amount of memory ZRAM can
228214
writeback_limit WO specifies the maximum amount of write IO zram
229215
can write out to backing device as 4KB unit
230216
writeback_limit_enable RW show and set writeback_limit feature
231-
max_comp_streams RW the number of possible concurrent compress
232-
operations
233217
comp_algorithm RW show and change the compression algorithm
234218
algorithm_params WO setup compression algorithm parameters
235219
compact WO trigger memory compaction
@@ -310,15 +294,15 @@ a single line of text and contains the following stats separated by whitespace:
310294
Unit: 4K bytes
311295
============== =============================================================
312296

313-
10) Deactivate
297+
9) Deactivate
314298
==============
315299

316300
::
317301

318302
swapoff /dev/zram0
319303
umount /dev/zram1
320304

321-
11) Reset
305+
10) Reset
322306
=========
323307

324308
Write any positive value to 'reset' sysfs node::

Documentation/admin-guide/cgroup-v1/memory.rst

+4
Original file line numberDiff line numberDiff line change
@@ -610,6 +610,10 @@ memory.stat file includes following statistics:
610610

611611
'rss + mapped_file" will give you resident set size of cgroup.
612612

613+
Note that some kernel configurations might account complete larger
614+
allocations (e.g., THP) towards 'rss' and 'mapped_file', even if
615+
only some, but not all that memory is mapped.
616+
613617
(Note: file and shmem may be shared among other cgroups. In that case,
614618
mapped_file is accounted only when the memory cgroup is owner of page
615619
cache.)

Documentation/admin-guide/cgroup-v2.rst

+23-2
Original file line numberDiff line numberDiff line change
@@ -1445,7 +1445,10 @@ The following nested keys are defined.
14451445

14461446
anon
14471447
Amount of memory used in anonymous mappings such as
1448-
brk(), sbrk(), and mmap(MAP_ANONYMOUS)
1448+
brk(), sbrk(), and mmap(MAP_ANONYMOUS). Note that
1449+
some kernel configurations might account complete larger
1450+
allocations (e.g., THP) if only some, but not all the
1451+
memory of such an allocation is mapped anymore.
14491452

14501453
file
14511454
Amount of memory used to cache filesystem data,
@@ -1488,7 +1491,10 @@ The following nested keys are defined.
14881491
Amount of application memory swapped out to zswap.
14891492

14901493
file_mapped
1491-
Amount of cached filesystem data mapped with mmap()
1494+
Amount of cached filesystem data mapped with mmap(). Note
1495+
that some kernel configurations might account complete
1496+
larger allocations (e.g., THP) if only some, but not
1497+
not all the memory of such an allocation is mapped.
14921498

14931499
file_dirty
14941500
Amount of cached filesystem data that was modified but
@@ -1560,6 +1566,12 @@ The following nested keys are defined.
15601566
workingset_nodereclaim
15611567
Number of times a shadow node has been reclaimed
15621568

1569+
pswpin (npn)
1570+
Number of pages swapped into memory
1571+
1572+
pswpout (npn)
1573+
Number of pages swapped out of memory
1574+
15631575
pgscan (npn)
15641576
Amount of scanned pages (in an inactive LRU list)
15651577

@@ -1575,6 +1587,9 @@ The following nested keys are defined.
15751587
pgscan_khugepaged (npn)
15761588
Amount of scanned pages by khugepaged (in an inactive LRU list)
15771589

1590+
pgscan_proactive (npn)
1591+
Amount of scanned pages proactively (in an inactive LRU list)
1592+
15781593
pgsteal_kswapd (npn)
15791594
Amount of reclaimed pages by kswapd
15801595

@@ -1584,6 +1599,9 @@ The following nested keys are defined.
15841599
pgsteal_khugepaged (npn)
15851600
Amount of reclaimed pages by khugepaged
15861601

1602+
pgsteal_proactive (npn)
1603+
Amount of reclaimed pages proactively
1604+
15871605
pgfault (npn)
15881606
Total number of page faults incurred
15891607

@@ -1661,6 +1679,9 @@ The following nested keys are defined.
16611679
pgdemote_khugepaged
16621680
Number of pages demoted by khugepaged.
16631681

1682+
pgdemote_proactive
1683+
Number of pages demoted by proactively.
1684+
16641685
hugetlb
16651686
Amount of memory used by hugetlb pages. This metric only shows
16661687
up if hugetlb usage is accounted for in memory.current (i.e.

Documentation/admin-guide/kernel-parameters.txt

+23-7
Original file line numberDiff line numberDiff line change
@@ -1866,7 +1866,7 @@
18661866
hpet_mmap= [X86, HPET_MMAP] Allow userspace to mmap HPET
18671867
registers. Default set by CONFIG_HPET_MMAP_DEFAULT.
18681868

1869-
hugepages= [HW] Number of HugeTLB pages to allocate at boot.
1869+
hugepages= [HW,EARLY] Number of HugeTLB pages to allocate at boot.
18701870
If this follows hugepagesz (below), it specifies
18711871
the number of pages of hugepagesz to be allocated.
18721872
If this is the first HugeTLB parameter on the command
@@ -1878,15 +1878,24 @@
18781878
<node>:<integer>[,<node>:<integer>]
18791879

18801880
hugepagesz=
1881-
[HW] The size of the HugeTLB pages. This is used in
1882-
conjunction with hugepages (above) to allocate huge
1883-
pages of a specific size at boot. The pair
1884-
hugepagesz=X hugepages=Y can be specified once for
1885-
each supported huge page size. Huge page sizes are
1886-
architecture dependent. See also
1881+
[HW,EARLY] The size of the HugeTLB pages. This is
1882+
used in conjunction with hugepages (above) to
1883+
allocate huge pages of a specific size at boot. The
1884+
pair hugepagesz=X hugepages=Y can be specified once
1885+
for each supported huge page size. Huge page sizes
1886+
are architecture dependent. See also
18871887
Documentation/admin-guide/mm/hugetlbpage.rst.
18881888
Format: size[KMG]
18891889

1890+
hugepage_alloc_threads=
1891+
[HW] The number of threads that should be used to
1892+
allocate hugepages during boot. This option can be
1893+
used to improve system bootup time when allocating
1894+
a large amount of huge pages.
1895+
The default value is 25% of the available hardware threads.
1896+
1897+
Note that this parameter only applies to non-gigantic huge pages.
1898+
18901899
hugetlb_cma= [HW,CMA,EARLY] The size of a CMA area used for allocation
18911900
of gigantic hugepages. Or using node format, the size
18921901
of a CMA area per node can be specified.
@@ -1897,6 +1906,13 @@
18971906
hugepages using the CMA allocator. If enabled, the
18981907
boot-time allocation of gigantic hugepages is skipped.
18991908

1909+
hugetlb_cma_only=
1910+
[HW,CMA,EARLY] When allocating new HugeTLB pages, only
1911+
try to allocate from the CMA areas.
1912+
1913+
This option does nothing if hugetlb_cma= is not also
1914+
specified.
1915+
19001916
hugetlb_free_vmemmap=
19011917
[KNL] Requires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
19021918
enabled.

0 commit comments

Comments
 (0)