[PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool

2021-12-06 Thread Baoquan He
In the current code, three atomic memory pools are always created, atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is specified in kernel command line. In fact, atomic pool is only necessary when CONFIG_DMA_DIRECT_REMAP=y or mem_encrypt_active=y which are needed on few ARCHes. So chang

Re: [PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool

2021-12-06 Thread John Donnelly
On 12/6/21 9:07 PM, Baoquan He wrote: In the current code, three atomic memory pools are always created, atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is specified in kernel command line. In fact, atomic pool is only necessary when CONFIG_DMA_DIRECT_REMAP=y or mem_encrypt_active=y w

Re: [PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool

2021-12-12 Thread Christoph Hellwig
On Tue, Dec 07, 2021 at 11:07:47AM +0800, Baoquan He wrote: > In the current code, three atomic memory pools are always created, > atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is > specified in kernel command line. In fact, atomic pool is only > necessary when CONFIG_DMA_DIRECT_REMAP

Re: [PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool

2021-12-13 Thread Baoquan He
On 12/13/21 at 08:44am, Christoph Hellwig wrote: > On Tue, Dec 07, 2021 at 11:07:47AM +0800, Baoquan He wrote: > > In the current code, three atomic memory pools are always created, > > atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is > > specified in kernel command line. In fact, ato