From: Roman Gushchin <guro@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Aslan Bakirov <aslan@fb.com>, Michal Hocko <mhocko@kernel.org>,
<linux-mm@kvack.org>, <kernel-team@fb.com>,
<linux-kernel@vger.kernel.org>, Rik van Riel <riel@surriel.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Roman Gushchin <guro@fb.com>
Subject: [PATCH v5 0/2] mm: using CMA for 1 GB hugepages allocation
Date: Tue, 7 Apr 2020 09:38:38 -0700 [thread overview]
Message-ID: <20200407163840.92263-1-guro@fb.com> (raw)
The patchset adds a hugetlb_cma boot option, which allows
to reserve a cma area which can be later used for 1 GB
hugepages allocations.
v5:
1) made the hugetlb_cma work if a cma reservation fails on some nodes
v4:
1) added a patch from Aslan, which is adding a useful function to cma
2) removed the hard-coded archs list from docs
3) added a warning printing on non-supported archs
4) hugetlb_lock is temporarily dropped in update_and_free_page()
Thanks!
Aslan Bakirov (1):
mm: cma: NUMA node interface
Roman Gushchin (1):
mm: hugetlb: optionally allocate gigantic hugepages using cma
.../admin-guide/kernel-parameters.txt | 8 ++
arch/arm64/mm/init.c | 6 +
arch/x86/kernel/setup.c | 4 +
include/linux/cma.h | 13 ++-
include/linux/hugetlb.h | 12 ++
include/linux/memblock.h | 3 +
mm/cma.c | 16 +--
mm/hugetlb.c | 109 ++++++++++++++++++
mm/memblock.c | 2 +-
9 files changed, 163 insertions(+), 10 deletions(-)
--
2.25.1
next reply other threads:[~2020-04-07 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 16:38 Roman Gushchin [this message]
2020-04-07 16:38 ` [PATCH v5 1/2] mm: cma: NUMA node interface Roman Gushchin
2020-04-09 0:53 ` Andrew Morton
2020-04-09 1:15 ` Roman Gushchin
2020-04-07 16:38 ` [PATCH v5 2/2] mm: hugetlb: optionally allocate gigantic hugepages using cma Roman Gushchin
2020-04-07 18:15 ` Michal Hocko
2020-04-07 18:42 ` Roman Gushchin
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=20200407163840.92263-1-guro@fb.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=aslan@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=riel@surriel.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: 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