diff options
| author | Mike Rapoport (IBM) <rppt@kernel.org> | 2023-03-22 09:17:27 +0100 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-04-06 04:42:47 +0200 |
| commit | 7ce6048d3a7d2f9b43f3d8a34a52e4122bdc2f23 (patch) | |
| tree | c10f1684e38ad8fe921bba6307bae917e9934c4f /arch | |
| parent | mm, treewide: redefine MAX_ORDER sanely (diff) | |
| download | linux-7ce6048d3a7d2f9b43f3d8a34a52e4122bdc2f23.tar.xz linux-7ce6048d3a7d2f9b43f3d8a34a52e4122bdc2f23.zip | |
loongarch: drop ranges for definition of ARCH_FORCE_MAX_ORDER
LoongArch 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.
Link: https://lkml.kernel.org/r/20230322081727.2516291-1-rppt@kernel.org
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Cc: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/loongarch/Kconfig | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/arch/loongarch/Kconfig b/arch/loongarch/Kconfig index 272a3a12c98d..e1e3a3828962 100644 --- a/arch/loongarch/Kconfig +++ b/arch/loongarch/Kconfig @@ -420,11 +420,8 @@ config NODES_SHIFT config ARCH_FORCE_MAX_ORDER int "Maximum zone order" - range 13 63 if PAGE_SIZE_64KB default "13" if PAGE_SIZE_64KB - range 11 63 if PAGE_SIZE_16KB default "11" if PAGE_SIZE_16KB - range 10 63 default "10" help The kernel memory allocator divides physically contiguous memory |