From: Michal Hocko <mhocko@kernel.org>
To: <linux-mm@kvack.org>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/4] mm, hugetlb: allow proper node fallback dequeue
Date: Tue, 13 Jun 2017 11:00:35 +0200 [thread overview]
Message-ID: <20170613090039.14393-1-mhocko@kernel.org> (raw)
Hi,
while working on a hugetlb migration issue addressed in a separate
patchset [1] I have noticed that the hugetlb allocations from the
preallocated pool are quite subotimal. There is no fallback mechanism
implemented and no notion of preferred node. I have tried to work
around it by [2] but Vlastimil was right to push back for a more robust
solution. It seems that such a solution is to reuse zonelist approach
we use for the page alloctor.
This series has 4 patches. The first one tries to make hugetlb
allocation layers more clear. The second one implements the zonelist
hugetlb pool allocation and introduces a preferred node semantic which
is used by the migration callbacks. The third patch is a pure clean up
as well as the last patch.
Note that this patch depends on [1] (without the last patch which
is replaced by this work). You can find the whole series in
git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git branch
attempts/hugetlb-zonelists
I am sending this as an RFC because I might be missing some subtle
dependencies which led to the original design.
Shortlog
Michal Hocko (4):
mm, hugetlb: unclutter hugetlb allocation layers
hugetlb: add support for preferred node to alloc_huge_page_nodemask
mm, hugetlb: get rid of dequeue_huge_page_node
mm, hugetlb, soft_offline: use new_page_nodemask for soft offline migration
And the diffstat looks promissing as well
include/linux/hugetlb.h | 3 +-
include/linux/migrate.h | 2 +-
mm/hugetlb.c | 233 ++++++++++++++++--------------------------------
mm/memory-failure.c | 10 +--
4 files changed, 82 insertions(+), 166 deletions(-)
[1] http://lkml.kernel.org/r/20170608074553.22152-1-mhocko@kernel.org
[2] http://lkml.kernel.org/r/20170608074553.22152-5-mhocko@kernel.org
next reply other threads:[~2017-06-13 9:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 9:00 Michal Hocko [this message]
2017-06-13 9:00 ` [RFC PATCH 1/4] mm, hugetlb: unclutter hugetlb allocation layers Michal Hocko
2017-06-14 13:18 ` Vlastimil Babka
2017-06-14 13:42 ` Michal Hocko
2017-06-14 14:04 ` Michal Hocko
2017-06-14 15:06 ` Vlastimil Babka
2017-06-14 15:28 ` Michal Hocko
2017-06-13 9:00 ` [RFC PATCH 2/4] hugetlb: add support for preferred node to alloc_huge_page_nodemask Michal Hocko
2017-06-14 16:17 ` Vlastimil Babka
2017-06-14 16:41 ` Michal Hocko
2017-06-14 16:57 ` Vlastimil Babka
2017-06-14 22:12 ` Mike Kravetz
2017-06-15 0:12 ` Mike Kravetz
2017-06-15 8:12 ` Michal Hocko
2017-06-13 9:00 ` [RFC PATCH 3/4] mm, hugetlb: get rid of dequeue_huge_page_node Michal Hocko
2017-06-13 9:00 ` [RFC PATCH 4/4] mm, hugetlb, soft_offline: use new_page_nodemask for soft offline migration Michal Hocko
2017-06-14 16:22 ` Vlastimil Babka
2017-06-16 11:44 ` [RFC PATCH 0/4] mm, hugetlb: allow proper node fallback dequeue Michal Hocko
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=20170613090039.14393-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=mgorman@suse.de \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vbabka@suse.cz \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).