public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Soumya Koduri <skoduri@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: Matt Benjamin <mbenjamin@redhat.com>
Subject: NFS client behavior on WRITE_DELEGATION
Date: Mon, 3 Dec 2018 13:22:59 +0530	[thread overview]
Message-ID: <68c7c07a-949d-1ce0-ec7e-5ab71ffaaa3b@redhat.com> (raw)

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

             reply	other threads:[~2018-12-03  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  7:52 Soumya Koduri [this message]
     [not found] ` <CAFX2JfmYMnKoiQ0Kjt8SGLx2H=3GwwtLHco0wMR4xVHkJpLaoQ@mail.gmail.com>
2018-12-05 20:30   ` NFS client behavior on WRITE_DELEGATION Anna Schumaker
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=68c7c07a-949d-1ce0-ec7e-5ab71ffaaa3b@redhat.com \
    --to=skoduri@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mbenjamin@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