diff options
| author | Feng Tang <feng.tang@linux.alibaba.com> | 2026-05-25 04:51:11 +0300 |
|---|---|---|
| committer | Marek Szyprowski <m.szyprowski@samsung.com> | 2026-05-28 11:11:45 +0300 |
| commit | d5cae2261b86913e602452ce4a07e6aefc0f603b (patch) | |
| tree | bbe5046e29684493b8f8871540a2dc05ac7e35ec /include/linux/stacktrace.h | |
| parent | 7e6ace2535d032c908e4d8747d9a7952617c001a (diff) | |
| download | linux-d5cae2261b86913e602452ce4a07e6aefc0f603b.tar.xz | |
dma-contiguous: simplify numa cma area handling
Currently, there are 2 kernel cmdline ways to setup numa cma area:
"cma_pernuma=" and "numa_cma=", and there are 2 cma arrays as well,
while they have no difference technically. Robin suggested to cleanup
the code and only use one array [1], as "the apparent intent that
users only want one _or_ the other".
Simplify the code by only using one array to save the numa cma area.
And in rare case that a user really setup the 2 cmdline parameters
at the same time, let the per-node specific size setting 'numa_cma='
take priority over the global numa cma setting.
Link[1]: https://lore.kernel.org/lkml/43c5301c-fe6a-41e4-9482-ccfc7b62f2a7@arm.com/
Suggested-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Link: https://lore.kernel.org/r/20260525015111.6267-1-feng.tang@linux.alibaba.com
Diffstat (limited to 'include/linux/stacktrace.h')
0 files changed, 0 insertions, 0 deletions
