From: Mike Rapoport <rppt@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Huacai Chen <chenhuacai@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Mike Rapoport <rppt@kernel.org>, WANG Xuerui <kernel@xen0n.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mips@vger.kernel.org
Subject: [PATCH] mips: drop ranges for definition of ARCH_FORCE_MAX_ORDER
Date: Wed, 22 Mar 2023 10:15:20 +0200 [thread overview]
Message-ID: <20230322081520.2516226-1-rppt@kernel.org> (raw)
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
MIPS defines insane ranges for ARCH_FORCE_MAX_ORDER allowing MAX_ORDER
up to 63, which implies maximal contiguous allocation size of 2^63
pages.
Drop bogus definitions of ranges for ARCH_FORCE_MAX_ORDER and leave it a
simple integer with sensible defaults.
Users that *really* need to change the value of ARCH_FORCE_MAX_ORDER
will be able to do so but they won't be mislead by the bogus ranges.
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---
arch/mips/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 3e8b765b8c7b..a0f6e9d0a561 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -2137,13 +2137,9 @@ endchoice
config ARCH_FORCE_MAX_ORDER
int "Maximum zone order"
- range 13 63 if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_64KB
default "13" if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_64KB
- range 12 63 if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_32KB
default "12" if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_32KB
- range 11 63 if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_16KB
default "11" if MIPS_HUGE_TLB_SUPPORT && PAGE_SIZE_16KB
- range 0 63
default "10"
help
The kernel memory allocator divides physically contiguous memory
--
2.35.1
next reply other threads:[~2023-03-22 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 8:15 Mike Rapoport [this message]
2023-03-22 8:24 ` Mike Rapoport
2023-03-22 8:59 ` Thomas Bogendoerfer
2023-03-22 10:02 ` Kirill A. Shutemov
2023-03-22 17:14 ` David Hildenbrand
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=20230322081520.2516226-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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