On 07/24/2017 03:58 PM, Michael Ellerman wrote:
"Aneesh Kumar K.V" <aneesh.ku...@linux.vnet.ibm.com> writes:
We don't support allocating them runtime. Only supported mechanism as of now is
HMC based hypervisor interface. So disable 16G hugetlb on powernv platform
Signed-off-by: Aneesh Kumar K.V <aneesh.ku...@linux.vnet.ibm.com>
---
May be this should go to -stable ?. To show the 16G pagesize in
/sys/kernel/mm/hugepages/ confuse users
It's a bit of a hack :/
16G also shows up on pseries, when there are no pages pre-allocated,
which is also confusing.
Ideally we'd only show sizes that can be allocated at runtime, OR were
preallocated, regardless of platform.
Is there an easy way to do that?
That is tricky, we are are going to enable 16G hugetlb on powernv with a
followup patch. In that series we depend on the specifying hugetlb page
count via kernel command line. The way above kernel command line parsing
work is by looking at the hugetlb hstate which got allocated before and
then assign the number of hugepages to that hstate. What you are asking
is to fail the creating of hstate based on number of hugepages.
For now there is no way of using 16G hugepage on powernv. This patch
address that issue by not showing 16G as a supported hugetlb page. In
the later series, we will enable 16G hugetlb for powernv
and at which point both pseries and powernv behavior will remain consistent.
-aneesh
