[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200922160218.GA10358@alpha.franken.de>
Date: Tue, 22 Sep 2020 18:02:18 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Paul Cercueil <paul@...pouillou.net>
Cc: od@...c.me, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Increase range of CONFIG_FORCE_MAX_ZONEORDER
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@...pouillou.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...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists