From: Christoph Hellwig <hch@infradead.org>
To: Dan Aloni <dan.aloni@vastdata.com>
Cc: anna@kernel.org, linux-nfs@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] nfs: add 'noalignwrite' option for lock-less 'lost writes' prevention
Date: Mon, 29 Jul 2024 08:08:29 -0700 [thread overview]
Message-ID: <ZqewbefiA_Duy_gz@infradead.org> (raw)
In-Reply-To: <20240724110712.2600130-1-dan.aloni@vastdata.com>
As mentioned last time my preference would still be if NFS did not
do this weird extension by default. But given that Trond like it
I suspect I'm unlikely to get that, so at least having an option
is a good thing:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-07-29 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 11:07 [PATCH] nfs: add 'noalignwrite' option for lock-less 'lost writes' prevention Dan Aloni
2024-07-29 15:08 ` Christoph Hellwig [this message]
2024-08-19 11:18 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 10:01 Dan Aloni
2024-06-27 11:06 ` Jeff Layton
2024-07-03 19:09 ` Sagi Grimberg
2024-07-11 8:06 ` Dan Aloni
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=ZqewbefiA_Duy_gz@infradead.org \
--to=hch@infradead.org \
--cc=anna@kernel.org \
--cc=dan.aloni@vastdata.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sagi@grimberg.me \
/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