Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Dan Aloni <dan.aloni@vastdata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] utils/mount/nfs.man: add noalignwrite
Date: Mon, 24 Mar 2025 16:28:21 -0400	[thread overview]
Message-ID: <da846f4b-8064-4519-a604-0f0214c48857@redhat.com> (raw)
In-Reply-To: <20250310125214.2592313-1-dan.aloni@vastdata.com>



On 3/10/25 8:52 AM, Dan Aloni wrote:
> Signed-off-by: Dan Aloni <dan.aloni@vastdata.com>
Committed... (tag: nfs-utils-2-8-3-rc8)

steved
> ---
>   utils/mount/nfs.man | 11 +++++++++++
>   1 file changed, 11 insertions(+)
> 
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index eab4692a87de..b5c5913bf315 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 buffered write operations
> +to full page boundaries.
> +.IP
> +Normally, the NFS client rounds non-aligned buffered writes up to the system
> +page size, 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 buffered 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.


      reply	other threads:[~2025-03-24 20:28 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
2025-03-10 12:52   ` [PATCH v2] " Dan Aloni
2025-03-24 20:28     ` Steve Dickson [this message]

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=da846f4b-8064-4519-a604-0f0214c48857@redhat.com \
    --to=steved@redhat.com \
    --cc=dan.aloni@vastdata.com \
    --cc=linux-nfs@vger.kernel.org \
    /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