Pull-request to address bug in mm/page_alloc.c
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-nvidia-6.5 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The current calculation of min_free_kbytes only uses ZONE_DMA and
ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_
also divide part of min_free_
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_
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
ZONE_DMA 1 8
ZONE_DMA32 151 709
ZONE_NORMAL 233 1113
ZONE_MOVABLE 1434 128
min_free_kbytes 7288 7326
Changed in linux-nvidia-6.5 (Ubuntu): | |
status: | New → Fix Released |
tags: | added: verification-done-jammy |
This bug is awaiting verification that the linux-nvidia- 6.5/6.5. 0-1014. 14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux- nvidia- 6.5' to 'verification- done-jammy- linux-nvidia- 6.5'. If the problem still exists, change the tag 'verification- needed- jammy-linux- nvidia- 6.5' to 'verification- failed- jammy-linux- nvidia- 6.5'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!