Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Dan Aloni <dan.aloni@vastdata.com>, steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] utils/mount/nfs.man: add noalignwrite
Date: Mon, 10 Mar 2025 08:12:26 -0400	[thread overview]
Message-ID: <c1ba003f46c0d9b59dcb6d1bd0afdb94b5f7df3f.camel@kernel.org> (raw)
In-Reply-To: <20250310120414.2515090-1-dan.aloni@vastdata.com>

On Mon, 2025-03-10 at 14:04 +0200, Dan Aloni wrote:
> Signed-off-by: Dan Aloni <dan.aloni@vastdata.com>
> ---
>  utils/mount/nfs.man | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index eab4692a87de..744411688641 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -618,6 +618,17 @@ option is not specified,
>  the default behavior depends on the kernel version,
>  but is usually equivalent to
>  .BR "xprtsec=none" .
> +.TP 1.5i
> +.BI noalignwrite
> +This option disables the default behavior of extending write operations to full
> +page boundaries.
> +.IP
> +Normally, the NFS client rounds non-aligned writes up to the system page size,

Isn't that only true for buffered writes? That should probably be made
clear if so.

> +which can lead to "lost writes" when multiple clients write concurrently
> +to distinct non-overlapping regions. Use this option when your
> +applications perform non-aligned writes and you can guarantee that file
> +regions do not overlap, thus avoiding the need for file locking.
> +.IP
>  .SS "Options for NFS versions 2 and 3 only"
>  Use these options, along with the options in the above subsection,
>  for NFS versions 2 and 3 only.

-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-03-10 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 12:04 [PATCH] utils/mount/nfs.man: add noalignwrite Dan Aloni
2025-03-10 12:12 ` Jeff Layton [this message]
2025-03-10 12:52   ` [PATCH v2] " Dan Aloni
2025-03-24 20:28     ` Steve Dickson

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=c1ba003f46c0d9b59dcb6d1bd0afdb94b5f7df3f.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=dan.aloni@vastdata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.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