public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@RedHat.com>
To: trondmy@kernel.org, Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Add a mount option to support eager writes
Date: Sat, 13 Feb 2021 09:19:05 -0500	[thread overview]
Message-ID: <d6d6c503-cdae-db31-45d4-e05fe46f0a2a@RedHat.com> (raw)
In-Reply-To: <20210212214949.4408-1-trondmy@kernel.org>

Hey!

On 2/12/21 4:49 PM, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
> 
> The following patch series sets up a new mount option
> 'writes=lazy/eager/wait'. The mount option basically controls how the
> write() system call works.
> - writes=lazy is the default, and keeps the current behaviour
> - writes=eager means we send off the write immediately as an unstable
>   write to the server.
> - writes=wait means we send off the write as an unstable write, and then
>   wait for the reply.
> 
> The main motivator for this behaviour is that some applications expect
> write() to return ENOSPC. Setting writes=wait should satisfy those
> applications without taking the full overhead of a synchronous write.
> 
> writes=eager, on the other hand, can be useful for applications such as
> re-exporting NFS, since it would allow knfsd on the proxying server to
> immediately forward the writes to the original server.
> 
> Trond Myklebust (3):
>   NFS: 'flags' field should be unsigned in struct nfs_server
>   NFS: Add support for eager writes
>   NFS: Add mount options supporting eager writes
> 
>  fs/nfs/file.c             | 19 +++++++++++++++++--
>  fs/nfs/fs_context.c       | 33 +++++++++++++++++++++++++++++++++
>  fs/nfs/write.c            | 17 ++++++++++++-----
>  include/linux/nfs_fs_sb.h |  4 +++-
>  4 files changed, 65 insertions(+), 8 deletions(-)
> 
Shouldn't something be added to the nfs(5) man page 
as well as blurb added to /etc/nfsmount.conf file?

steved. 


  parent reply	other threads:[~2021-02-13 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 21:49 [PATCH 0/3] Add a mount option to support eager writes trondmy
2021-02-12 21:49 ` [PATCH 1/3] NFS: 'flags' field should be unsigned in struct nfs_server trondmy
2021-02-12 21:49   ` [PATCH 2/3] NFS: Add support for eager writes trondmy
2021-02-12 21:49     ` [PATCH 3/3] NFS: Add mount options supporting " trondmy
2021-02-13 14:19 ` Steve Dickson [this message]
2021-02-13 14:20   ` [PATCH 0/3] Add a mount option to support " Trond Myklebust

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=d6d6c503-cdae-db31-45d4-e05fe46f0a2a@RedHat.com \
    --to=steved@redhat.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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