RFC mm, hugetlb: allocation API and migration improvements
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | mm, hugetlb: unify core page allocation accounting and initializationmm/ | +29 | 1 reply | |
| 2/5 | mm, hugetlb: integrate giga hugetlb more naturally to the allocation pathmm/ | +12 | 1 reply | |
| 3/5 | mm, hugetlb: do not rely on overcommit limit during migrationinclude/ mm/ mm/ | +99 | 3 replies | |
| 4/5 | mm, hugetlb: get rid of surplus page accounting tricksmm/ | +21 | 3 replies | |
| 5/5 | mm, hugetlb: further simplify hugetlb allocation APImm/ | +41 | 1 reply |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Mike Kravetz | Naoya Horiguchi |
|---|---|---|
| Series | R-b R-b | R-b R-b |
| 1/5 | R-b | |
| 2/5 | R-b | |
| 3/5 | R-b | |
| 4/5 | R-b | |
| 5/5 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH 0/5] mm, hugetlb: allocation API and migration improvements
Hi,
this is a follow up for [1] for the allocation API and [2] for the hugetlb migration. It wasn't really easy to split those into two separate patch series as they share some code.
My primary motivation to touch this code is to make the gigantic pages migration working. The giga pages allocation code is just too fragile and hacked into the hugetlb code now. This series tries to move giga pages closer to the first class citizen. We are not there yet but having 5 patches is quite a lot already and it will already make the code much easier to follow. I will come with other changes on top after this sees some review.
The first two patches should be trivial to review. The third patch changes the way how we migrate huge pages. Newly allocated pages are a subject of the overcommit check and they participate surplus accounting which is quite unfortunate as the changelog explains. This patch doesn't change anything wrt. giga pages.
Patch #4 removes the surplus accounting hack from __alloc_surplus_huge_page. I hope I didn't miss anything there and a deeper review is really due there.
Patch #5 finally unifies allocation paths and giga pages shouldn't be any special anymore. There is also some renaming going on as well.
Shortlog
Michal Hocko (5):
mm, hugetlb: unify core page allocation accounting and initialization mm, hugetlb: integrate giga hugetlb more naturally to the allocation path mm, hugetlb: do not rely on overcommit limit during migration mm, hugetlb: get rid of surplus page accounting tricks
mm, hugetlb: further simplify hugetlb allocation API
Diffstat:
include/linux/hugetlb.h | 3 + mm/hugetlb.c | 305 +++++++++++++++++++++++++++--------------------- mm/migrate.c | 3 +- 3 files changed, 175 insertions(+), 136 deletions(-)
[1] http://lkml.kernel.org/r/[email protected]
[2] http://lkml.kernel.org/r/[email protected]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>