Thread (50 messages) 50 messages, 9 authors, 2021-08-09

Re: [RFC PATCH 12/15] mm: Make MAX_ORDER of buddy allocator configurable via Kconfig SET_MAX_ORDER.

From: Vlastimil Babka <hidden>
Date: 2021-08-06 15:17:03
Also in: lkml

On 8/5/21 9:02 PM, Zi Yan wrote:
From: Zi Yan <ziy@nvidia.com>
+config SET_MAX_ORDER
+	int "Set maximum order of buddy allocator"
+    depends on SPARSEMEM_VMEMMAP && (ARCH_FORCE_MAX_ORDER = 0)
+	range 11 255
+	default "11"
+	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.
+
+	  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.
It's enough that it's confusing for the devs, we could spare the users and add
+1 to the value they specify :)
 config HAVE_MEMBLOCK_PHYS_MAP
 	bool
 
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help