From: Mike Kravetz <mike.kravetz@oracle.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Will Deacon <will@kernel.org>, Roman Gushchin <guro@fb.com>
Cc: Barry Song <song.bao.hua@hisilicon.com>,
Catalin Marinas <catalin.marinas@arm.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, linux-mm@kvack.org,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"H.Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
akpm@linux-foundation.org, Mike Rapoport <rppt@linux.ibm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] mm/hugetlb: split hugetlb_cma in nodes with memory
Date: Mon, 27 Jul 2020 10:52:49 -0700 [thread overview]
Message-ID: <523426cd-1586-5d57-9650-134a2ac30d16@oracle.com> (raw)
In-Reply-To: <874kptm3b4.fsf@linux.ibm.com>
On 7/27/20 7:37 AM, Aneesh Kumar K.V wrote:
> There is variant of this which is pseries powerpc where there is
> hypervisor assistance w.r.t allocating gigantic pages. See the ppc64
> enablement patch
>
> https://lore.kernel.org/linuxppc-dev/20200713150749.25245-1-aneesh.kumar@linux.ibm.com/
>
Thanks Aneesh, I missed the powerpc support.
I knew about the powerpc hypervisor assistance which caused me to rethink
my original idea that all this could be arch independent. My next idea was
that architectures would only need to provide a constant something like:
#define HUGETLB_CMA_ORDER (PUD_SHIFT - PAGE_SHIFT)
However, it looks like this can not be a compile time constant on powerpc.
Moving more of the CMA support to arch independent code has moved down on
my priority list. So, it it likely not to get much work in the immediate
future.
Just curious, can you have multiple gigantic page sizes supported at one
time (one system instance) on powerpc?
--
Mike Kravetz
next prev parent reply other threads:[~2020-07-27 17:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:09 Barry Song
2020-07-14 23:21 ` Mike Kravetz
2020-07-15 8:18 ` Will Deacon
2020-07-15 16:59 ` Mike Kravetz
2020-07-16 8:12 ` Will Deacon
2020-07-16 18:25 ` Mike Kravetz
2020-07-17 5:02 ` Anshuman Khandual
2020-07-17 8:36 ` Will Deacon
2020-07-17 9:51 ` Anshuman Khandual
2020-07-17 17:37 ` Mike Kravetz
2020-07-20 6:14 ` Anshuman Khandual
2020-07-17 17:02 ` Mike Kravetz
2020-07-20 6:22 ` Anshuman Khandual
2020-07-20 18:17 ` Mike Kravetz
2020-07-27 14:37 ` Aneesh Kumar K.V
2020-07-27 17:52 ` Mike Kravetz [this message]
2020-07-15 11:14 ` Song Bao Hua (Barry Song)
2020-07-15 17:05 ` Mike Kravetz
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=523426cd-1586-5d57-9650-134a2ac30d16@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=guro@fb.com \
--cc=hpa@zytor.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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