From: Jerry Snitselaar jsnitsel@redhat.com
redhat/configs: remove CONFIG_DMA_PERNUMA_CMA and switch CONFIG_DMA_NUMA_CMA off
CONFIG_DMA_PERNUMA_CMA was replaced by CONFIG_DMA_NUMA_CMA, so remove the old, and continue to leave off with CONFIG_DMA_NUMA_CMA.
Signed-off-by: Jerry Snitselaar jsnitsel@redhat.com
diff --git a/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA b/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA +++ b/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA @@ -1 +1 @@ -CONFIG_DMA_NUMA_CMA=y +# CONFIG_DMA_NUMA_CMA is not set diff --git a/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA b/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_DMA_PERNUMA_CMA is not set
-- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099
From: Donald Dutile on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099#note_1895021...
What memory does enabling these CONFIG's to yes consume? or does it 'just' turn on the ability to use CMA areas, and (per-numa) cma- size has to be set to consume memory?
From: Jerry Snitselaar on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099#note_1895025...
I am going to look at that this week, and try to get some good data on it, but wanted to keep it in sync with the previous behavior from CONFIG_DMA_PERNUMA_CMA for now while that is figured out.
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099#note_1903033...
@jsnitsel @ddutile - we are rebasing today. Is this worth approving and merging today or just wait and rebase tomorrow?
From: Jerry Snitselaar on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099#note_1903246...
I guess this already resolved itself? :smile:
kernel@lists.fedoraproject.org