From: Trond Myklebust <trondmy@hammerspace.com>
To: "rick.macklem@gmail.com" <rick.macklem@gmail.com>,
"hch@infradead.org" <hch@infradead.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"tao.lyu@epfl.ch" <tao.lyu@epfl.ch>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: Question about O_APPEND | O_DIRECT
Date: Tue, 28 Nov 2023 18:28:13 +0000 [thread overview]
Message-ID: <6d6ba42df68d4639742ed42a00bd08ea608892a6.camel@hammerspace.com> (raw)
In-Reply-To: <ZWXmcYy8NElP0FC2@infradead.org>
On Tue, 2023-11-28 at 05:09 -0800, Christoph Hellwig wrote:
> On Mon, Nov 27, 2023 at 05:50:49PM -0800, Rick Macklem wrote:
> > > > Well, it does support O_RDWR|O_APPEND, just not with O_DIRECT?
> > > >
> > > > Btw, I think an APPEND operation in NFS would be a very good
> > > > idea, and
> > > > I'd love to work with interested parties in the IETF on it.
> > It is not easy to deal with w.r.t. RPC retries.
>
> Indeed.
>
> > I suppose a NFSv4.2 extension that either requires (or strongly
> > recommends) persistent sessions might work?
> > (Persistent sessions should pretty well guarantee an RPC is not
> > redone on the server.)
>
> I guess so. That of course actually means we rely on a viable
> implementation of persistent sessions. The Linux server doesn't
> support them, and I'm not sure which servers actually do.
Nobody is going to implement the overhead of persistent sessions just
in order to add support for APPEND.
The only thing that will be achieved by tying the functionality to
persistent sessions is to ensure that people will completely ignore the
spec.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2023-11-28 18:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 18:14 Question about O_APPEND | O_DIRECT Tao Lyu
2023-11-25 23:54 ` Trond Myklebust
2023-11-27 15:28 ` Tao Lyu
2023-11-27 16:36 ` Christoph Hellwig
2023-11-27 16:41 ` Tao Lyu
2023-11-27 16:50 ` Chuck Lever III
2023-11-27 16:55 ` Christoph Hellwig
2023-11-27 16:59 ` Chuck Lever III
2023-11-28 13:06 ` Christoph Hellwig
2023-11-28 1:50 ` Rick Macklem
2023-11-28 13:09 ` Christoph Hellwig
2023-11-28 18:28 ` Trond Myklebust [this message]
2023-11-27 17:08 ` Trond Myklebust
2023-11-27 17:19 ` hch
2023-11-27 17:23 ` Tao Lyu
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=6d6ba42df68d4639742ed42a00bd08ea608892a6.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rick.macklem@gmail.com \
--cc=tao.lyu@epfl.ch \
/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