mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-01-04 04:04:19 +00:00
mm/cma: make MAX_CMA_AREAS = CONFIG_CMA_AREAS
There is no real difference between the global area, and other additionally configured CMA areas via CONFIG_CMA_AREAS that always defaults without user input. This makes MAX_CMA_AREAS same as CONFIG_CMA_AREAS, also incrementing its default values, thus maintaining current default for MAX_CMA_AREAS both for UMA and NUMA systems. Link: https://lkml.kernel.org/r/20240205051929.298559-1-anshuman.khandual@arm.com Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
fe58582c0e
commit
73307523c9
@ -6,12 +6,8 @@
|
||||
#include <linux/types.h>
|
||||
#include <linux/numa.h>
|
||||
|
||||
/*
|
||||
* There is always at least global CMA area and a few optional
|
||||
* areas configured in kernel .config.
|
||||
*/
|
||||
#ifdef CONFIG_CMA_AREAS
|
||||
#define MAX_CMA_AREAS (1 + CONFIG_CMA_AREAS)
|
||||
#define MAX_CMA_AREAS CONFIG_CMA_AREAS
|
||||
#endif
|
||||
|
||||
#define CMA_MAX_NAME 64
|
||||
|
@ -917,14 +917,14 @@ config CMA_SYSFS
|
||||
config CMA_AREAS
|
||||
int "Maximum count of the CMA areas"
|
||||
depends on CMA
|
||||
default 19 if NUMA
|
||||
default 7
|
||||
default 20 if NUMA
|
||||
default 8
|
||||
help
|
||||
CMA allows to create CMA areas for particular purpose, mainly,
|
||||
used as device private area. This parameter sets the maximum
|
||||
number of CMA area in the system.
|
||||
|
||||
If unsure, leave the default value "7" in UMA and "19" in NUMA.
|
||||
If unsure, leave the default value "8" in UMA and "20" in NUMA.
|
||||
|
||||
config MEM_SOFT_DIRTY
|
||||
bool "Track memory changes"
|
||||
|
Loading…
Reference in New Issue
Block a user