@@ -896,7 +896,7 @@ config DATA_SHIFT
896
896
8M pages will be pinned.
897
897
898
898
config ARCH_FORCE_MAX_ORDER
899
- int "Maximum zone order "
899
+ int "Order of maximal physically contiguous allocations "
900
900
range 7 8 if PPC64 && PPC_64K_PAGES
901
901
default "8" if PPC64 && PPC_64K_PAGES
902
902
range 12 12 if PPC64 && !PPC_64K_PAGES
@@ -910,17 +910,19 @@ config ARCH_FORCE_MAX_ORDER
910
910
range 10 63
911
911
default "10"
912
912
help
913
- The kernel memory allocator divides physically contiguous memory
914
- blocks into "zones", where each zone is a power of two number of
915
- pages. This option selects the largest power of two that the kernel
916
- keeps in the memory allocator. If you need to allocate very large
917
- blocks of physically contiguous memory, then you may need to
918
- increase this value .
913
+ The kernel page allocator limits the size of maximal physically
914
+ contiguous allocations. The limit is called MAX_ORDER and it
915
+ defines the maximal power of two of number of pages that can be
916
+ allocated as a single contiguous block. This option allows
917
+ overriding the default setting when ability to allocate very
918
+ large blocks of physically contiguous memory is required .
919
919
920
920
The page size is not necessarily 4KB. For example, on 64-bit
921
921
systems, 64KB pages can be enabled via CONFIG_PPC_64K_PAGES. Keep
922
922
this in mind when choosing a value for this option.
923
923
924
+ Don't change if unsure.
925
+
924
926
config PPC_SUBPAGE_PROT
925
927
bool "Support setting protections for 4k subpages (subpage_prot syscall)"
926
928
default n
0 commit comments