From: "Christian König" <christian.koenig@amd.com>
To: wangtao <tao.wangtao@honor.com>, "T.J. Mercier" <tjmercier@google.com>
Cc: "sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
"benjamin.gaignard@collabora.com"
<benjamin.gaignard@collabora.com>,
"Brian.Starkey@arm.com" <Brian.Starkey@arm.com>,
"jstultz@google.com" <jstultz@google.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wangbintian(BintianWang)" <bintian.wang@honor.com>,
yipengxiang <yipengxiang@honor.com>,
liulu 00013167 <liulu.liu@honor.com>,
hanfeng 00012985 <feng.han@honor.com>,
"amir73il@gmail.com" <amir73il@gmail.com>
Subject: Re: [PATCH 2/2] dmabuf/heaps: implement DMA_BUF_IOCTL_RW_FILE for system_heap
Date: Wed, 21 May 2025 13:56:46 +0200 [thread overview]
Message-ID: <d786ff9f-9bf0-42e1-987f-f2091fd90279@amd.com> (raw)
In-Reply-To: <e61fcdbf71ba4f9dbfef2f521d1b2fc1@honor.com>
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.
next prev parent reply other threads:[~2025-05-21 11:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 9:28 wangtao
2025-05-13 11:32 ` Christian König
2025-05-13 12:30 ` wangtao
2025-05-13 13:17 ` Christian König
2025-05-14 11:02 ` wangtao
2025-05-14 12:00 ` Christian König
2025-05-15 14:03 ` wangtao
2025-05-15 14:26 ` Christian König
2025-05-16 7:40 ` wangtao
2025-05-16 8:36 ` Christian König
2025-05-16 9:49 ` wangtao
2025-05-16 10:29 ` Christian König
2025-05-19 4:08 ` wangtao
2025-05-19 7:47 ` Christian König
2025-05-16 18:37 ` T.J. Mercier
2025-05-19 4:37 ` wangtao
2025-05-19 12:03 ` wangtao
2025-05-20 4:06 ` wangtao
2025-05-21 2:00 ` T.J. Mercier
2025-05-21 4:17 ` wangtao
2025-05-21 7:35 ` Christian König
2025-05-21 10:25 ` wangtao
2025-05-21 11:56 ` Christian König [this message]
2025-05-22 8:02 ` wangtao
2025-05-22 11:57 ` Christian König
2025-05-22 12:29 ` wangtao
2025-05-27 14:35 ` wangtao
2025-05-27 15:10 ` Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d786ff9f-9bf0-42e1-987f-f2091fd90279@amd.com \
--to=christian.koenig@amd.com \
--cc=Brian.Starkey@arm.com \
--cc=amir73il@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=bintian.wang@honor.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=feng.han@honor.com \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liulu.liu@honor.com \
--cc=sumit.semwal@linaro.org \
--cc=tao.wangtao@honor.com \
--cc=tjmercier@google.com \
--cc=yipengxiang@honor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®