Messages in this thread Patch in this message | | | From | Jay Chen <> | Subject | [RFC PATCH] provide per numa cma with an initial default size | Date | Tue, 30 Nov 2021 15:45:56 +0800 |
| |
In the actual production environment, when we open cma and per numa cma, if we do not increase the per numa size configuration in cmdline, we find that our performance has dropped by 20%. Through analysis, we found that the default size of per numa is 0, which causes the driver to allocate memory from cma, which affects performance. Therefore, we think we need to provide a default size.
Signed-off-by: Jay Chen <jkchen@linux.alibaba.com> --- kernel/dma/contiguous.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c index 3d63d91cba5c..3bef8bf371d9 100644 --- a/kernel/dma/contiguous.c +++ b/kernel/dma/contiguous.c @@ -99,7 +99,7 @@ early_param("cma", early_cma); #ifdef CONFIG_DMA_PERNUMA_CMA static struct cma *dma_contiguous_pernuma_area[MAX_NUMNODES]; -static phys_addr_t pernuma_size_bytes __initdata; +static phys_addr_t pernuma_size_bytes __initdata = size_bytes; static int __init early_cma_pernuma(char *p) { -- 2.27.0
| |