On 28/11/16 17:16, Aneesh Kumar K.V wrote: > W.r.t hash page table config, we support 16MB and 16GB as the hugepage > size. Update the hstate_get_psize to handle 16M and 16G. > > Signed-off-by: Aneesh Kumar K.V <aneesh.ku...@linux.vnet.ibm.com> > --- > arch/powerpc/include/asm/book3s/64/hugetlb.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/arch/powerpc/include/asm/book3s/64/hugetlb.h > b/arch/powerpc/include/asm/book3s/64/hugetlb.h > index 499268045306..d9c283f95e05 100644 > --- a/arch/powerpc/include/asm/book3s/64/hugetlb.h > +++ b/arch/powerpc/include/asm/book3s/64/hugetlb.h > @@ -21,6 +21,10 @@ static inline int hstate_get_psize(struct hstate *hstate) > return MMU_PAGE_2M; > else if (shift == mmu_psize_defs[MMU_PAGE_1G].shift) > return MMU_PAGE_1G; > + else if (shift == mmu_psize_defs[MMU_PAGE_16M].shift) > + return MMU_PAGE_16M; > + else if (shift == mmu_psize_defs[MMU_PAGE_16G].shift) > + return MMU_PAGE_16G;
Could we reorder this We check for 2M, 1G, 16M and 16G. The likely sizes are 2M and 16M. Can we have those upfront so that the order of checks is 2M, 16M, 1G and 16G Balbir
