mm: Don't set and reset page count in MEMINIT_EARLY
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest2 patches 31 repliesIn review
- v32 patches 3 repliesSuperseded
- v22 patches 1 replySuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 4 patches | 4 replies | Superseded |
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm: pass page count and reserved to __init_single_pagemm/ mm/ mm/ | +21 | 2 replies | |
| 2/2 | mm: Init page count in reserve_bootmem_region when MEMINIT_EARLYmm/ mm/ | +25 | 29 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [PATCH v4 0/2] mm: Don't set and reset page count in MEMINIT_EARLY
__init_single_page would set page count and __free_pages_core would reset 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 pass page count and reserved to __init_single_page. It's in preparation for the 2nd patch, it didn't change anything.
The 2nd patch only set page count for the reserved region, not all of the region.
Yajun Deng (2):
mm: pass page count and reserved to __init_single_page
mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY
mm/hugetlb.c | 2 +- mm/internal.h | 8 +++++++- mm/mm_init.c | 38 ++++++++++++++++++++++++-------------- mm/page_alloc.c | 20 ++++++++++++-------- 4 files changed, 44 insertions(+), 24 deletions(-)
Signature · 1 line
2.25.1