diff options
| author | Anshuman Khandual <[email protected]> | 2024-02-05 10:49:29 +0530 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-02-22 10:24:53 -0800 |
| commit | 73307523c9bbc4e3b35f0058cdbc15e32bd83c52 (patch) | |
| tree | 98526f63a92ae83e4411e00068c5d02afd2a45e6 /include/linux | |
| parent | fe58582c0e362d5e52b97985142b0dcef920b745 (diff) | |
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/[email protected]
Signed-off-by: Anshuman Khandual <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'include/linux')
| -rw-r--r-- | include/linux/cma.h | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/include/linux/cma.h b/include/linux/cma.h index 63873b93deaa..9db877506ea8 100644 --- a/include/linux/cma.h +++ b/include/linux/cma.h @@ -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 |