diff options
| author | liuq <[email protected]> | 2023-06-25 03:16:56 +0000 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2023-08-18 17:12:07 +0000 |
| commit | 416ef04fe00c5f2f6fb8e13d8dbe1b5a0a274f83 (patch) | |
| tree | 1f03ef95311aa32095524943caa3d2251541107f /mm/mm_init.c | |
| parent | fs: convert block_commit_write to return void (diff) | |
| download | kernel-416ef04fe00c5f2f6fb8e13d8dbe1b5a0a274f83.tar.gz kernel-416ef04fe00c5f2f6fb8e13d8dbe1b5a0a274f83.zip | |
mm/page_alloc: fix min_free_kbytes calculation regarding ZONE_MOVABLE
The current calculation of min_free_kbytes only uses ZONE_DMA and
ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN] will
also divide part of min_free_kbytes.This will cause the min watermark of
ZONE_NORMAL to be too small in the presence of ZONE_MOVEABLE.
__GFP_HIGH and PF_MEMALLOC allocations usually don't need movable zone
pages, so just like ZONE_HIGHMEM, cap pages_min to a small value in
__setup_per_zone_wmarks().
On my testing machine with 16GB of memory (transparent hugepage is turned
off by default, and movablecore=12G is configured) The following is a
comparative test data of watermark_min
no patch add patch
ZONE_DMA 1 8
ZONE_DMA32 151 709
ZONE_NORMAL 233 1113
ZONE_MOVABLE 1434 128
min_free_kbytes 7288 7326
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: liuq <[email protected]>
Reviewed-by: "Huang, Ying" <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'mm/mm_init.c')
0 files changed, 0 insertions, 0 deletions