From: Christoph Hellwig <hch@infradead.org>
To: Rick Macklem <rick.macklem@gmail.com>
Cc: Chuck Lever III <chuck.lever@oracle.com>,
Christoph Hellwig <hch@infradead.org>, Tao Lyu <tao.lyu@epfl.ch>,
Trond Myklebust <trondmy@hammerspace.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Question about O_APPEND | O_DIRECT
Date: Tue, 28 Nov 2023 05:09:05 -0800 [thread overview]
Message-ID: <ZWXmcYy8NElP0FC2@infradead.org> (raw)
In-Reply-To: <CAM5tNy4qVXXS3sHqx7Y3Ndt2YNnd1hrj32iJdo9KMi+ByMfEuQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-11-28 13:09 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 [this message]
2023-11-28 18:28 ` Trond Myklebust
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=ZWXmcYy8NElP0FC2@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rick.macklem@gmail.com \
--cc=tao.lyu@epfl.ch \
--cc=trondmy@hammerspace.com \
/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