Linux NFS development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Chuck Lever <cel@kernel.org>,
	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: Fri, 5 Dec 2025 00:05:07 -0800	[thread overview]
Message-ID: <aTKSMwu9RFGYfNoK@infradead.org> (raw)
In-Reply-To: <6b29d6fb-04e8-43da-bc1d-0e78572b5402@oracle.com>

On Thu, Dec 04, 2025 at 10:10:39AM -0800, Dai Ngo wrote:
> > 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?

Using the same persistent reservation mechanism as the SCSI layout.
The very minor difference in the registration scope are transparently
handled by the drivers.


  reply	other threads:[~2025-12-05  8:05 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
2025-12-05  8:05       ` Christoph Hellwig [this message]
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=aTKSMwu9RFGYfNoK@infradead.org \
    --to=hch@infradead.org \
    --cc=cel@kernel.org \
    --cc=dai.ngo@oracle.com \
    --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