From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"dan.aloni@vastdata.com" <dan.aloni@vastdata.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs: add 'noextend' option for lock-less 'lost writes' prevention
Date: Wed, 19 Jun 2024 22:27:18 -0700 [thread overview]
Message-ID: <ZnO9toGg3ARR3e8V@infradead.org> (raw)
In-Reply-To: <50f63382-eeb1-4615-a0ac-987afee11902@grimberg.me>
On Wed, Jun 19, 2024 at 05:31:08PM +0300, Sagi Grimberg wrote:
> > buffered I/O model. So this would allow the user or sysadmin to specify
> > at file creation time that this file will be used for purposes that are
> > incompatible with caching.
>
> user/sysadmin as in not the client? setting this out-of-band?
> That does not work where the application and the sysadmin do not know about
> each other (i.e. in a cloud environment).
>
> The use-case that is described here cannot be mandated by the server because
> the file usage pattern is really driven by the application.
The way I understood Trond is that it is set on the client, but the
application or and out of band tool. Think of the attributes set by
chattr.
next prev parent reply other threads:[~2024-06-20 5:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 15:33 [PATCH] nfs: add 'noextend' option for lock-less 'lost writes' prevention Dan Aloni
2024-06-18 18:59 ` Trond Myklebust
2024-06-19 8:37 ` Sagi Grimberg
2024-06-19 14:15 ` Trond Myklebust
2024-06-19 14:31 ` Sagi Grimberg
2024-06-20 5:27 ` Christoph Hellwig [this message]
2024-06-20 6:41 ` Sagi Grimberg
2024-06-20 5:26 ` Christoph Hellwig
2024-06-19 5:44 ` Christoph Hellwig
2024-06-19 13:33 ` Trond Myklebust
2024-06-19 18:03 ` Trond Myklebust
2024-06-20 5:13 ` hch
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=ZnO9toGg3ARR3e8V@infradead.org \
--to=hch@infradead.org \
--cc=dan.aloni@vastdata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sagi@grimberg.me \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.