From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Li Wang <liwang@kylinos.cn>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
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] misc: fgds: enable GPU-NVMe direct I/O via POSIX and io_uring
Date: Wed, 9 Sep 2026 15:35:59 +0200 [thread overview]
Message-ID: <2026090924-corsage-shout-833d@gregkh> (raw)
In-Reply-To: <6aed7ecf-d125-40d1-a82d-1a7f62049605@kylinos.cn>
On Wed, Sep 09, 2026 at 06:42:03PM +0800, Li Wang wrote:
> Hi Greg,
> Thanks for the review!
>
> >
> > That's not really needed in a changelog text, it could be in the 0/X
> > patch :)
> >
> Sorry for the clutter. I will move most of them into the 0/X patch in v2.
>
> > Anyway, you didn't cc: the io_uring list, why?
> >
> `scripts/get_maintainer.pl` didn't output the io_uring mailing list, likely
> because this patch doesn't directly touch the io_uring codebase itself. It only
> enables remapping GPU memory buffers to CPU virtual addresses, which can then be
> consumed via standard io_uring APIs.
>
> I've added io-uring@vger.kernel.org to CC for this reply and will keep it in v2.
Great, as you are using that as the api, there might be some parts that
will need to be reviewed by them.
> > Nor why "fgds" is the name, that's going to be hard to remember, does it
> > stand for something?
> >
> "FGDS" stands for Fast GPUDirect Storage. GPUDirect Storage (GDS) is NVIDIA's
> technology enabling direct I/O between GPU memory and files on NVMe,
> widely used in LLM workloads to bypass CPU overhead.
That's nvidia's specific solution, but this works on other devices,
right? Or just for that one platform?
And you are using this as a "bypass" for the normal accel subsystem,
shouldn't this be part of that subsystem instead of a custom user/kernel
api like you are creating here?
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-09 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260908131545.105987-1-liwang@kylinos.cn>
[not found] ` <2026090913-landline-encroach-c544@gregkh>
2026-09-09 10:42 ` [RFC PATCH] misc: fgds: enable GPU-NVMe direct I/O via POSIX and io_uring Li Wang
2026-09-09 13:35 ` Greg Kroah-Hartman [this message]
2026-09-09 13:45 ` Christian König
2026-09-10 3:57 ` Li Wang
2026-09-10 8:35 ` 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=2026090924-corsage-shout-833d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.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=liwang@kylinos.cn \
--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