From: Anna Schumaker <schumaker.anna@gmail.com>
To: Anna Schumaker <schumakeranna@gmail.com>,
Soumya Koduri <skoduri@redhat.com>
Cc: linux-nfs@vger.kernel.org, Matt Benjamin <mbenjamin@redhat.com>
Subject: Re: NFS client behavior on WRITE_DELEGATION
Date: Wed, 05 Dec 2018 15:30:02 -0500 [thread overview]
Message-ID: <0c94d447b8c8901a1d7c5fa4cffcf5d7b3960e86.camel@gmail.com> (raw)
In-Reply-To: <CAFX2JfmYMnKoiQ0Kjt8SGLx2H=3GwwtLHco0wMR4xVHkJpLaoQ@mail.gmail.com>
(Resending due to accidentally using HTML instead of plain text)
On Wed, 2018-12-05 at 15:22 -0500, Anna Schumaker wrote:
> Hi Soumya,
>
> What conditions are you seeing the writes? It could be the kernel trying to
> flush out data to free up memory for other processes.
>
> I don't think preemptively writing back data is necessarily a bad thing
> though, even with a write delegation. If the server decides to recall the
> delegation, we wouldn't keep it waiting as long while we write back local
> data. Additionally, if the client crashes then any updates might have already
> had a chance to sync to the server.
>
> I hope this helps!
> Anna
>
> On Mon, Dec 3, 2018 at 2:55 AM Soumya Koduri <skoduri@redhat.com> wrote:
> > Hi,
> >
> > In our NFSv4.1 Delegations testing we observed that NFS client sends
> > WRITE requests to the server even when granted WRITE_DELEGATION. I see
> > that only OPEN/CLOSE and LOCK operations are served locally by the client.
> >
> > Please confirm if this behavior is expected and if yes, can it be
> > improved to avoid sending WRITEs to the server until the application
> > does fsync.
> >
> > Thanks,
> > Soumya
next prev parent reply other threads:[~2018-12-05 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 7:52 NFS client behavior on WRITE_DELEGATION Soumya Koduri
[not found] ` <CAFX2JfmYMnKoiQ0Kjt8SGLx2H=3GwwtLHco0wMR4xVHkJpLaoQ@mail.gmail.com>
2018-12-05 20:30 ` Anna Schumaker [this message]
2018-12-06 15:10 ` Soumya Koduri
2018-12-07 15:06 ` Soumya Koduri
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=0c94d447b8c8901a1d7c5fa4cffcf5d7b3960e86.camel@gmail.com \
--to=schumaker.anna@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mbenjamin@redhat.com \
--cc=schumakeranna@gmail.com \
--cc=skoduri@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