mm: Don't init and clear page count when MEMINIT_EARLY
Get series with b4
b4 am [email protected]Versions newest first
- v5 Latest2 patches 0 repliesNew
Patches in v5 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm: allow optional initialization of page count and PG_reserved flagmm/ mm/ mm/ | +21 | 0 replies | |
| 2/2 | mm: Init page count in reserve_bootmem_region when MEMINIT_EARLYmm/ mm/ | +27 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCH v5 0/2] mm: Don't init and clear page count when MEMINIT_EARLY
__init_single_page would init page count and __free_pages_core would clear it. A lot of pages don't need to do this when in MEMINIT_EARLY context. It's unnecessary and time-consuming.
The 1st patch is allow optional initialization of page count and PG_reserved flag. It's in preparation for the 2nd patch, it didn't change anything.
The 2nd patch only init page count for the reserved region, not all of the region when MEMINIT_EARLY.
Yajun Deng (2):
mm: allow optional initialization of page count and PG_reserved flag
mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY
mm/hugetlb.c | 2 +- mm/internal.h | 8 +++++++- mm/mm_init.c | 40 ++++++++++++++++++++++++++-------------- mm/page_alloc.c | 20 ++++++++++++-------- 4 files changed, 46 insertions(+), 24 deletions(-)
Signature · 1 line
2.25.1