[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aD7x_b0hVyvZDUsl@infradead.org>
Date: Tue, 3 Jun 2025 06:00:45 -0700
From: Christoph Hellwig <hch@...radead.org>
To: wangtao <tao.wangtao@...or.com>
Cc: sumit.semwal@...aro.org, christian.koenig@....com, kraxel@...hat.com,
vivek.kasireddy@...el.com, viro@...iv.linux.org.uk,
brauner@...nel.org, hughd@...gle.com, akpm@...ux-foundation.org,
amir73il@...il.com, benjamin.gaignard@...labora.com,
Brian.Starkey@....com, jstultz@...gle.com, tjmercier@...gle.com,
jack@...e.cz, baolin.wang@...ux.alibaba.com,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
bintian.wang@...or.com, yipengxiang@...or.com, liulu.liu@...or.com,
feng.han@...or.com
Subject: Re: [PATCH v4 0/4] Implement dmabuf direct I/O via copy_file_range
This is a really weird interface. No one has yet to explain why dmabuf
is so special that we can't support direct I/O to it when we can support
it to otherwise exotic mappings like PCI P2P ones.
Powered by blists - more mailing lists