From: Li Wang <liwang@kylinos.cn>
To: "Pavel Begunkov" <asml.silence@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Christian König" <christian.koenig@amd.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mengmeng Zhao <zhaomengmeng@kylinos.cn>
Subject: Re: [RFC PATCH v2 0/1] misc: fgds: introduce GPU-File direct I/O via dma-buf
Date: Wed, 28 Oct 2026 11:01:17 +0800 [thread overview]
Message-ID: <36d782c9-d8a2-410e-8bb8-36bb6e9f9549@kylinos.cn> (raw)
In-Reply-To: <749e9437-85a6-45fa-b984-b155a1eeddaf@gmail.com>
Hi all,
On 27/10/2026 21:54, Pavel Begunkov wrote:
> Hey Li,
>
> On 10/27/26 09:08, Li Wang wrote:
...
>
> xfs support it a it orthogonal to the uapi question, but it should be
> implemented in xfs and not side stepped. There is an RFC on the mailing
> list from Anuj and Nitesh that is trying to do that.
> Thanks for the feedback!
As far as we know, Pavel's current work only supports direct data transfer
between GPU memory and NVMe raw block devices. As Pavel pointed out, I
tended to prefer an implementation that was as non-intrusive to the
filesystem as possible. My rationale was that GPU-NVME direct data transfer
would ideally not require filesystem opt-in, since there was no readahead,
no caching, and no complex metadata operations involved here. In most cases,
the filesystem merely helps translate file offsets into disk block addresses.
Additionally, adopting an ioctl interface had a smaller impact scope and
provided a simpler userspace synchronous operation interface.
We will track the community progress, and we appreciate being let know if
there is anything we can help contribute to, as we are active users of
this feature.
Thanks,
Li Wang
prev parent reply other threads:[~2026-10-28 3:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:15 [RFC PATCH] misc: fgds: enable GPU-NVMe direct I/O via POSIX and io_uring Li Wang
2026-09-09 6:10 ` Greg Kroah-Hartman
2026-09-09 10:42 ` Li Wang
2026-09-09 13:35 ` Greg Kroah-Hartman
2026-09-09 13:45 ` Christian König
2026-09-10 3:57 ` Li Wang
2026-09-10 8:35 ` Christian König
2026-09-12 12:45 ` Pavel Begunkov
2026-10-27 9:08 ` [RFC PATCH v2 0/1] misc: fgds: introduce GPU-File direct I/O via dma-buf Li Wang
2026-10-27 9:08 ` [RFC PATCH v2 1/1] " Li Wang
2026-10-27 13:03 ` Jens Axboe
2026-10-27 13:12 ` Greg Kroah-Hartman
2026-10-27 13:12 ` Christian König
2026-10-27 13:54 ` [RFC PATCH v2 0/1] " Pavel Begunkov
2026-10-28 3:01 ` Li Wang [this message]
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=36d782c9-d8a2-410e-8bb8-36bb6e9f9549@kylinos.cn \
--to=liwang@kylinos.cn \
--cc=arnd@arndb.de \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=zhaomengmeng@kylinos.cn \
/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®