From: Dai Ngo <dai.ngo@oracle.com>
To: Christoph Hellwig <hch@infradead.org>, Chuck Lever <cel@kernel.org>
Cc: Zhou Jifeng <zhoujifeng@kylinsec.com.cn>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: Can the PNFS blocklayout of the Linux nfsd server be used in a production environment?
Date: Thu, 4 Dec 2025 10:10:39 -0800 [thread overview]
Message-ID: <6b29d6fb-04e8-43da-bc1d-0e78572b5402@oracle.com> (raw)
In-Reply-To: <aS6ChyDRx-hALj5V@infradead.org>
On 12/1/25 10:09 PM, Christoph Hellwig wrote:
> As the author of much of the block* layout code I agree with Chuck, just
> want to throw in a little extra note:
>
> On Thu, Nov 27, 2025 at 11:40:50AM -0500, Chuck Lever wrote:
>> NFSD's pNFS block layout with NVMe implementation is fresh from the
>> factory (I think the implementation went into v6.12?). As with
>> iSCSI/SCSI, try it and see if it works well enough for you.
> So while the NVMe layout support is indeed very new, it's also very
> little code, on the server side the support is entirely contained in
> the nvme driver by implementing the get_unique_id method (~60 lines of
> code) and on the client side it is looking for the nvme persistent
> devices names (2 Lines of code after a small preparatory refactoring).
>
> So in general I think it should be taken as the same maturity as the
> SCSI layout at this point.
How does server fence a client using NVMe layout?
-Dai
next prev parent reply other threads:[~2025-12-04 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 2:14 Can the PNFS blocklayout of the Linux nfsd server be used in a production environment? Zhou Jifeng
2025-11-27 16:40 ` Chuck Lever
2025-11-28 8:12 ` Zhou Jifeng
2025-11-28 16:17 ` Chuck Lever
2025-11-28 8:57 ` LAYOUT4_NFSV4_1_FILES supported? " Sebastian Feld
2025-11-28 16:23 ` Chuck Lever
2025-11-28 23:16 ` Rick Macklem
2025-12-01 15:11 ` Chuck Lever
2025-12-02 6:09 ` Christoph Hellwig
2025-12-04 18:10 ` Dai Ngo [this message]
2025-12-05 8:05 ` Christoph Hellwig
2025-12-05 18:50 ` Dai Ngo
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=6b29d6fb-04e8-43da-bc1d-0e78572b5402@oracle.com \
--to=dai.ngo@oracle.com \
--cc=cel@kernel.org \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=zhoujifeng@kylinsec.com.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