diff options
| author | Anshuman Khandual <anshuman.khandual@arm.com> | 2024-02-05 10:49:29 +0530 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2024-02-22 10:24:53 -0800 |
| commit | 73307523c9bbc4e3b35f0058cdbc15e32bd83c52 (patch) | |
| tree | 98526f63a92ae83e4411e00068c5d02afd2a45e6 /mm/Kconfig | |
| parent | fe58582c0e362d5e52b97985142b0dcef920b745 (diff) | |
| download | linux-stable-73307523c9bbc4e3b35f0058cdbc15e32bd83c52.tar.gz linux-stable-73307523c9bbc4e3b35f0058cdbc15e32bd83c52.tar.bz2 linux-stable-73307523c9bbc4e3b35f0058cdbc15e32bd83c52.zip | |
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>
Diffstat (limited to 'mm/Kconfig')
| -rw-r--r-- | mm/Kconfig | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/mm/Kconfig b/mm/Kconfig index 35fa9940e61f..88ba99d84ac3 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -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" |