Skip to content

Commit 7a5b272

Browse files
rpptakpm00
authored andcommitted
m68k: 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/[email protected] Signed-off-by: Mike Rapoport (IBM) <[email protected]> Acked-by: Kirill A. Shutemov <[email protected]> Acked-by: Geert Uytterhoeven <[email protected]> Reviewed-by: Zi Yan <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Catalin Marinas <[email protected]> Cc: Christophe Leroy <[email protected]> Cc: David Miller <[email protected]> Cc: Dinh Nguyen <[email protected]> Cc: Guo Ren <[email protected]> Cc: John Paul Adrian Glaubitz <[email protected]> Cc: Max Filippov <[email protected]> Cc: Michael Ellerman <[email protected]> Cc: Rich Felker <[email protected]> Cc: "Russell King (Oracle)" <[email protected]> Cc: Will Deacon <[email protected]> Cc: Yoshinori Sato <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
1 parent 9d0f7a5 commit 7a5b272

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

arch/m68k/Kconfig.cpu

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -398,21 +398,23 @@ config SINGLE_MEMORY_CHUNK
398398
Say N if not sure.
399399

400400
config ARCH_FORCE_MAX_ORDER
401-
int "Maximum zone order" if ADVANCED
401+
int "Order of maximal physically contiguous allocations" if ADVANCED
402402
depends on !SINGLE_MEMORY_CHUNK
403403
default "10"
404404
help
405-
The kernel memory allocator divides physically contiguous memory
406-
blocks into "zones", where each zone is a power of two number of
407-
pages. This option selects the largest power of two that the kernel
408-
keeps in the memory allocator. If you need to allocate very large
409-
blocks of physically contiguous memory, then you may need to
410-
increase this value.
405+
The kernel page allocator limits the size of maximal physically
406+
contiguous allocations. The limit is called MAX_ORDER and it
407+
defines the maximal power of two of number of pages that can be
408+
allocated as a single contiguous block. This option allows
409+
overriding the default setting when ability to allocate very
410+
large blocks of physically contiguous memory is required.
411411

412412
For systems that have holes in their physical address space this
413413
value also defines the minimal size of the hole that allows
414414
freeing unused memory map.
415415

416+
Don't change if unsure.
417+
416418
config 060_WRITETHROUGH
417419
bool "Use write-through caching for 68060 supervisor accesses"
418420
depends on ADVANCED && M68060

0 commit comments

Comments
 (0)