From: Trond Myklebust <trondmy@hammerspace.com>
To: "SteveD@RedHat.com" <SteveD@RedHat.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] Add a mount option to support eager writes
Date: Sat, 13 Feb 2021 14:20:56 +0000 [thread overview]
Message-ID: <bf54d0b012686cc424ed4e3f1f8891bd2ab48dfc.camel@hammerspace.com> (raw)
In-Reply-To: <d6d6c503-cdae-db31-45d4-e05fe46f0a2a@RedHat.com>
On Sat, 2021-02-13 at 09:19 -0500, Steve Dickson wrote:
> 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?
>
Sure, but I'd like comments/consensus on the kernel bits first. 🙂
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2021-02-13 14:21 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 ` [PATCH 0/3] Add a mount option to support " Steve Dickson
2021-02-13 14:20 ` Trond Myklebust [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=bf54d0b012686cc424ed4e3f1f8891bd2ab48dfc.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=SteveD@RedHat.com \
--cc=anna.schumaker@netapp.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