From: Paul Cercueil <paul@crapouillou.net>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: od@zcrc.me, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Increase range of CONFIG_FORCE_MAX_ZONEORDER
Date: Tue, 22 Sep 2020 19:11:48 +0200 [thread overview]
Message-ID: <O3L2HQ.37Y7OUPZFQDO1@crapouillou.net> (raw)
In-Reply-To: <20200922160218.GA10358@alpha.franken.de>
Hi Thomas,
Le mar. 22 sept. 2020 à 18:02, Thomas Bogendoerfer
<tsbogend@alpha.franken.de> a écrit :
> On Thu, Sep 17, 2020 at 03:35:28PM +0200, Paul Cercueil wrote:
>> There is nothing that prevents us from using lower maximum values.
>> It's something that we actually want, when using bigger page sizes
>> on
>> devices with low RAM.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>> arch/mips/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
>> index 632fe8fe68c4..dca2bbdbfc24 100644
>> --- a/arch/mips/Kconfig
>> +++ b/arch/mips/Kconfig
>> @@ -2251,7 +2251,7 @@ config FORCE_MAX_ZONEORDER
>> default "13" if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_32KB
>> range 12 64 if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_16KB
>> default "12" if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_16KB
>> - range 11 64
>> + range 0 64
>
> Do we need the range at all ? Most other archs don't use a range...
The maximum contiguous block size cannot be lower than a huge page, so
that's why the 'range' are here.
Which makes me think that there should probably be a "range 11 64 if
MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_8KB" and the same for 4KB pages.
With a lower value and huge pages enabled in the config, the kernel
probably would not boot.
Cheers,
-Paul
next prev parent reply other threads:[~2020-09-22 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:35 Paul Cercueil
2020-09-22 16:02 ` Thomas Bogendoerfer
2020-09-22 17:11 ` Paul Cercueil [this message]
2020-09-27 9:04 ` Thomas Bogendoerfer
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=O3L2HQ.37Y7OUPZFQDO1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=od@zcrc.me \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®