Re: [PATCH 6/7] drivers/migrate_offload: add DMA batch copy driver (dcbm)

[Garg, Shivank]

On 6/9/2026 5:30 AM, Karim Manaouil wrote:
> [You don't often get email from kmanaouil.dev@xxxxxxxxx. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> In my opinion the driver should be at drivers/dma/dcbm, other DMA drivers
> in the same directory like idxd and sdxi can just export a struct
> dma_migrator. It makes it easy to have everything in the driver's own
> directory. For example, idxd has some internals headers as well as an
> already existing dmaengine implementation in drivers/dma/idxd.
> 
> PS. I am writing an implementation of this based on idxd. I'll try to
> post it soon with numbers.
> 
> You can add
> Reviewed-by: Karim Manaouil <kmanaouil.dev@xxxxxxxxx>
> 

Hi Karim,

Thanks for the review.

I'm excited to see your idxd based implementation.

For plain memory to memory copy, which is all migration needs right now,
the public dmaengine API is good enough, and idxd/sdxi/ptdma ... can
all work through it. I'm curious which features you're planning to use
from idxd internal headers that dmaengine can't provide?

Also, my understanding is that driver/dma houses DMA providers,
whereas DCBM would be consumer of DMAengine APIs. So is that right
place for it?

Best regards,
Shivank