From: Dan Aloni <dan.aloni@vastdata.com>
To: Trond Myklebust <trondmy@hammerspace.com>,
Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] nfs: add 'noalignwrite' option for lock-less 'lost writes' prevention
Date: Thu, 11 Jul 2024 11:06:05 +0300 [thread overview]
Message-ID: <20240711080605.tvnimzndq4kuhp6l@gmail.com> (raw)
In-Reply-To: <1e66a583-f18f-41ed-b87c-9e7b4045e009@grimberg.me>
On 2024-07-03 22:09:58, Sagi Grimberg wrote:
>
>
> On 27/06/2024 13:01, Dan Aloni wrote:
> > There are some applications that write to predefined non-overlapping
> > file offsets from multiple clients and therefore don't need to rely on
> > file locking. However, if these applications want non-aligned offsets
> > and sizes they need to either use locks or risk data corruption, as the
> > NFS client defaults to extending writes to whole pages.
> >
> > This commit adds a new mount option `noalignwrite`, which allows to turn
> > that off and avoid the need of locking, as long as these applications
> > don't overlap on offsets.
> >
> > Signed-off-by: Dan Aloni <dan.aloni@vastdata.com>
>
> The new name seems a better choice.
> I'm also on Christoph's camp that having this behavior be the default makes
> sense given that we have large folios.
>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
>
>
> Trond, Anna,
> What are your thoughts on this?
Pinging. Do we need to do anything further? I can prepare the nfs-utils
patch too.
--
Dan Aloni
next prev parent reply other threads:[~2024-07-11 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:01 [PATCH] nfs: add 'noalignwrite' option for lock-less 'lost writes' prevention Dan Aloni
2024-06-27 11:06 ` Jeff Layton
2024-07-03 19:09 ` Sagi Grimberg
2024-07-11 8:06 ` Dan Aloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 11:07 Dan Aloni
2024-07-29 15:08 ` Christoph Hellwig
2024-08-19 11:18 ` Sagi Grimberg
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=20240711080605.tvnimzndq4kuhp6l@gmail.com \
--to=dan.aloni@vastdata.com \
--cc=anna@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox