Merge tag 'mm-stable-2023-04-27-15-30' of git://git.kernel.org/pub/scm/linux/kernel...

[linux-block.git] / arch / m68k / Kconfig.cpu

diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index 96a0fb4f1af53f38fd4dbeacc1aa8c768ab55f75..b826e9c677b2ae02539da10b62908b33139d03bd 100644 (file)
--- a/arch/m68k/Kconfig.cpu
+++ b/arch/m68k/Kconfig.cpu
@@ -397,23 +397,22 @@ config SINGLE_MEMORY_CHUNK
          Say N if not sure.
 
 config ARCH_FORCE_MAX_ORDER
-       int "Maximum zone order" if ADVANCED
+       int "Order of maximal physically contiguous allocations" if ADVANCED
        depends on !SINGLE_MEMORY_CHUNK
-       default "11"
+       default "10"
        help
-         The kernel memory allocator divides physically contiguous memory
-         blocks into "zones", where each zone is a power of two number of
-         pages.  This option selects the largest power of two that the kernel
-         keeps in the memory allocator.  If you need to allocate very large
-         blocks of physically contiguous memory, then you may need to
-         increase this value.
+         The kernel page allocator limits the size of maximal physically
+         contiguous allocations. The limit is called MAX_ORDER and it
+         defines the maximal power of two of number of pages that can be
+         allocated as a single contiguous block. This option allows
+         overriding the default setting when ability to allocate very
+         large blocks of physically contiguous memory is required.
 
          For systems that have holes in their physical address space this
          value also defines the minimal size of the hole that allows
          freeing unused memory map.
 
-         This config option is actually maximum order plus one. For example,
-         a value of 11 means that the largest free memory block is 2^10 pages.
+         Don't change if unsure.
 
 config 060_WRITETHROUGH
        bool "Use write-through caching for 68060 supervisor accesses"