[PATCH 2/2] dmabuf/heaps: implement DMA_BUF_IOCTL_RW_FILE for system_heap
Christian König
christian.koenig at amd.com
Wed May 21 11:56:46 UTC 2025
On 5/21/25 12:25, wangtao wrote:
> [wangtao] I previously explained that read/sendfile/splice/copy_file_range
> syscalls can't achieve dmabuf direct IO zero-copy.
And why can't you work on improving those syscalls instead of creating a new IOCTL?
> My focus is enabling dmabuf direct I/O for [regular file] <--DMA--> [dmabuf]
> zero-copy.
Yeah and that focus is wrong. You need to work on a general solution to the issue and not specific to your problem.
> Any API achieving this would work. Are there other uAPIs you think
> could help? Could you recommend experts who might offer suggestions?
Well once more: Either work on sendfile or copy_file_range or eventually splice to make it what you want to do.
When that is done we can discuss with the VFS people if that approach is feasible.
But just bypassing the VFS review by implementing a DMA-buf specific IOCTL is a NO-GO. That is clearly not something you can do in any way.
Regards,
Christian.
More information about the dri-devel
mailing list