powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text
The prompt and help text of ARCH_FORCE_MAX_ORDER are not even close to describe this configuration option. Update both to actually describe what this option does. Link: https://lkml.kernel.org/r/20230324052233.2654090-10-rppt@kernel.org Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Reviewed-by: Zi Yan <ziy@nvidia.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Christophe Leroy <christophe.leroy@csgroup.eu> Cc: David Miller <davem@davemloft.net> Cc: Dinh Nguyen <dinguyen@kernel.org> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Guo Ren <guoren@kernel.org> Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: Max Filippov <jcmvbkbc@gmail.com> Cc: Michael Ellerman <mpe@ellerman.id.au> Cc: Rich Felker <dalias@libc.org> Cc: "Russell King (Oracle)" <linux@armlinux.org.uk> Cc: Will Deacon <will@kernel.org> Cc: Yoshinori Sato <ysato@users.sourceforge.jp> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
482f7b7652
commit
6fc54303aa
@ -896,7 +896,7 @@ config DATA_SHIFT
|
|||||||
8M pages will be pinned.
|
8M pages will be pinned.
|
||||||
|
|
||||||
config ARCH_FORCE_MAX_ORDER
|
config ARCH_FORCE_MAX_ORDER
|
||||||
int "Maximum zone order"
|
int "Order of maximal physically contiguous allocations"
|
||||||
range 7 8 if PPC64 && PPC_64K_PAGES
|
range 7 8 if PPC64 && PPC_64K_PAGES
|
||||||
default "8" if PPC64 && PPC_64K_PAGES
|
default "8" if PPC64 && PPC_64K_PAGES
|
||||||
range 12 12 if PPC64 && !PPC_64K_PAGES
|
range 12 12 if PPC64 && !PPC_64K_PAGES
|
||||||
@ -910,17 +910,19 @@ config ARCH_FORCE_MAX_ORDER
|
|||||||
range 10 63
|
range 10 63
|
||||||
default "10"
|
default "10"
|
||||||
help
|
help
|
||||||
The kernel memory allocator divides physically contiguous memory
|
The kernel page allocator limits the size of maximal physically
|
||||||
blocks into "zones", where each zone is a power of two number of
|
contiguous allocations. The limit is called MAX_ORDER and it
|
||||||
pages. This option selects the largest power of two that the kernel
|
defines the maximal power of two of number of pages that can be
|
||||||
keeps in the memory allocator. If you need to allocate very large
|
allocated as a single contiguous block. This option allows
|
||||||
blocks of physically contiguous memory, then you may need to
|
overriding the default setting when ability to allocate very
|
||||||
increase this value.
|
large blocks of physically contiguous memory is required.
|
||||||
|
|
||||||
The page size is not necessarily 4KB. For example, on 64-bit
|
The page size is not necessarily 4KB. For example, on 64-bit
|
||||||
systems, 64KB pages can be enabled via CONFIG_PPC_64K_PAGES. Keep
|
systems, 64KB pages can be enabled via CONFIG_PPC_64K_PAGES. Keep
|
||||||
this in mind when choosing a value for this option.
|
this in mind when choosing a value for this option.
|
||||||
|
|
||||||
|
Don't change if unsure.
|
||||||
|
|
||||||
config PPC_SUBPAGE_PROT
|
config PPC_SUBPAGE_PROT
|
||||||
bool "Support setting protections for 4k subpages (subpage_prot syscall)"
|
bool "Support setting protections for 4k subpages (subpage_prot syscall)"
|
||||||
default n
|
default n
|
||||||
|
Loading…
Reference in New Issue
Block a user