From: Michael Ellerman <mpe@ellerman.id.au>
To: santhosh <santhog4@linux.vnet.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Rashmica Gupta <rashmicy@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Cc: manvanth@linux.vnet.ibm.com
Subject: Re: [V2] powerpc/Kconfig: Update config option based on page size.
Date: Fri, 16 Sep 2016 09:26:50 +1000 [thread overview]
Message-ID: <877facoibp.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <0d167ff1-cc0e-35bc-479c-aec77d2c8556@linux.vnet.ibm.com>
santhosh <santhog4@linux.vnet.ibm.com> writes:
>> Michael Ellerman <mpe@ellerman.id.au> writes:
>>
>>> On Fri, 2016-19-02 at 05:38:47 UTC, Rashmica Gupta wrote:
>>>> Currently on PPC64 changing kernel pagesize from 4K to 64K leaves
>>>> FORCE_MAX_ZONEORDER set to 13 - which produces a compile error.
>>>>
>>> ...
>>>> So, update the range of FORCE_MAX_ZONEORDER from 9-64 to 8-9 for 64K pages
>>>> and from 13-64 to 9-13 for 4K pages.
>>>
>>> https://git.kernel.org/powerpc/c/a7ee539584acf4a565b7439cea
>>>
>> HPAGE_PMD_ORDER is not something we should check w.r.t 4k linux page
>> size. We do have the below constraint w.r.t hugetlb pages
>>
>> static inline bool hstate_is_gigantic(struct hstate *h)
>> {
>> return huge_page_order(h) >= MAX_ORDER;
>> }
>>
>> That require MAX_ORDER to be greater than 12.
So have you tried that fix?
cheers
next prev parent reply other threads:[~2016-09-15 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 5:38 [PATCH V2] powerpc/Kconfig: Update config option based on page size Rashmica Gupta
2016-02-19 6:07 ` Balbir Singh
2016-04-11 12:35 ` [V2] " Michael Ellerman
2016-04-19 14:59 ` Aneesh Kumar K.V
2016-04-19 23:09 ` Balbir Singh
2016-09-14 10:40 ` santhosh
2016-09-15 23:26 ` Michael Ellerman [this message]
2016-09-16 6:03 ` Balbir Singh
2016-09-16 15:16 ` Aneesh Kumar K.V
2016-09-19 7:15 ` Balbir Singh
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=877facoibp.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manvanth@linux.vnet.ibm.com \
--cc=rashmicy@gmail.com \
--cc=santhog4@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).