From: Michal Hocko <mhocko@kernel.org> To: <linux-mm@kvack.org> Cc: Mike Kravetz <mike.kravetz@oracle.com>, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>, Andrew Morton <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org> Subject: [RFC PATCH 0/5] mm, hugetlb: allocation API and migration improvements Date: Mon, 4 Dec 2017 15:01:12 +0100 [thread overview] Message-ID: <20171204140117.7191-1-mhocko@kernel.org> (raw) 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/20170622193034.28972-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20171122152832.iayefrlxbugphorp@dhcp22.suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: linux-mm@kvack.org Cc: Mike Kravetz <mike.kravetz@oracle.com>, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>, Andrew Morton <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org> Subject: [RFC PATCH 0/5] mm, hugetlb: allocation API and migration improvements Date: Mon, 4 Dec 2017 15:01:12 +0100 [thread overview] Message-ID: <20171204140117.7191-1-mhocko@kernel.org> (raw) 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/20170622193034.28972-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20171122152832.iayefrlxbugphorp@dhcp22.suse.cz -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-12-04 14:01 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-04 14:01 Michal Hocko [this message] 2017-12-04 14:01 ` [RFC PATCH 0/5] mm, hugetlb: allocation API and migration improvements Michal Hocko 2017-12-04 14:01 ` [RFC PATCH 1/5] mm, hugetlb: unify core page allocation accounting and initialization Michal Hocko 2017-12-04 14:01 ` Michal Hocko 2017-12-13 0:20 ` Mike Kravetz 2017-12-13 0:20 ` Mike Kravetz 2017-12-04 14:01 ` [RFC PATCH 2/5] mm, hugetlb: integrate giga hugetlb more naturally to the allocation path Michal Hocko 2017-12-04 14:01 ` Michal Hocko 2017-12-13 0:24 ` Mike Kravetz 2017-12-13 0:24 ` Mike Kravetz 2017-12-04 14:01 ` [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration Michal Hocko 2017-12-04 14:01 ` Michal Hocko 2017-12-13 23:35 ` Mike Kravetz 2017-12-13 23:35 ` Mike Kravetz 2017-12-14 7:40 ` Michal Hocko 2017-12-14 7:40 ` Michal Hocko 2017-12-14 20:57 ` Mike Kravetz 2017-12-14 20:57 ` Mike Kravetz 2017-12-04 14:01 ` [RFC PATCH 4/5] mm, hugetlb: get rid of surplus page accounting tricks Michal Hocko 2017-12-04 14:01 ` Michal Hocko 2017-12-14 0:45 ` Mike Kravetz 2017-12-14 0:45 ` Mike Kravetz 2017-12-14 7:50 ` Michal Hocko 2017-12-14 7:50 ` Michal Hocko 2017-12-14 20:58 ` Mike Kravetz 2017-12-14 20:58 ` Mike Kravetz 2017-12-04 14:01 ` [RFC PATCH 5/5] mm, hugetlb: further simplify hugetlb allocation API Michal Hocko 2017-12-04 14:01 ` Michal Hocko 2017-12-14 21:01 ` Mike Kravetz 2017-12-14 21:01 ` Mike Kravetz 2017-12-15 9:33 ` [RFC PATCH 0/5] mm, hugetlb: allocation API and migration improvements Michal Hocko 2017-12-15 9:33 ` Michal Hocko 2017-12-20 5:33 ` Naoya Horiguchi 2017-12-20 5:33 ` Naoya Horiguchi 2017-12-20 9:53 ` Michal Hocko 2017-12-20 9:53 ` Michal Hocko 2017-12-20 22:43 ` Mike Kravetz 2017-12-20 22:43 ` Mike Kravetz 2017-12-21 7:28 ` Michal Hocko 2017-12-21 7:28 ` Michal Hocko 2017-12-21 23:35 ` Mike Kravetz 2017-12-21 23:35 ` Mike Kravetz 2017-12-22 9:48 ` Michal Hocko 2017-12-22 9:48 ` Michal Hocko 2017-12-22 8:58 ` Naoya Horiguchi 2017-12-22 8:58 ` Naoya Horiguchi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20171204140117.7191-1-mhocko@kernel.org \ --to=mhocko@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mike.kravetz@oracle.com \ --cc=n-horiguchi@ah.jp.nec.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.