From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Quentin Barnes <qbarnes+nfs@yahoo-inc.com>, linux-nfs@vger.kernel.org
Subject: Re: nfs_file_flush() question
Date: Mon, 18 Aug 2008 12:53:11 -0400 [thread overview]
Message-ID: <1219078391.7192.4.camel@localhost> (raw)
In-Reply-To: <309543F5-E522-44CC-B114-C9652328FE0F@oracle.com>
On Mon, 2008-08-18 at 12:04 -0400, Chuck Lever wrote:
> Does the Linux NFS client optimize away the GETATTR when it has sent
> only a single WRITE and the server has returned post-op attributes?
> Using a large wsize with a modern server implementation might make
> this a fairly common scenario.
Yes: please see the code. We use a standard nfs_revalidate_inode() which
will be optimised away if the inode metadata is known to be up to date.
Trond
next prev parent reply other threads:[~2008-08-18 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 0:23 nfs_file_flush() question Quentin Barnes
2008-08-17 17:04 ` Trond Myklebust
2008-08-18 16:04 ` Chuck Lever
2008-08-18 16:53 ` Trond Myklebust [this message]
2008-08-19 20:17 ` Quentin Barnes
2008-08-20 0:30 ` Trond Myklebust
2008-08-20 3:38 ` Quentin Barnes
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=1219078391.7192.4.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=qbarnes+nfs@yahoo-inc.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