From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: 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: Mon, 27 Nov 2023 08:55:35 -0800 [thread overview]
Message-ID: <ZWTKBzx2Wkw6Mbxd@infradead.org> (raw)
In-Reply-To: <7E2914D2-B9AB-4280-9A44-875DA8B58328@oracle.com>
On Mon, Nov 27, 2023 at 04:50:56PM +0000, Chuck Lever III wrote:
> > 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.
>
> You can write and submit a personal draft that describes it; it
> wouldn't need to be more than a few pages. The hard part of that
> would be accumulating use case descriptions.
>
> I think you could create a proof of concept by including a VERIFY
> operation in front of the WRITE to ensure the WRITE occurs only
> if the offset argument in the WRITE agrees with the file's size
> on the server. If the VERIFY fails, the client grabs the updated
> file size and tries again.
That seems like exactly the wrong idea around. The idea behind append
based models for write out of place storage is that you do not care
where it is written - you leave it to the server or storage device to
place it at the current append point. You just need to know where it
got placed after the fact for some of them (not for simply logs,
though).
next prev parent reply other threads:[~2023-11-27 16:55 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 [this message]
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
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=ZWTKBzx2Wkw6Mbxd@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--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