From: Sachin Prabhu <sprabhu@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: Should we be aggressively invalidating cache when using -onolock?
Date: Mon, 20 Sep 2010 11:15:56 -0400 (EDT) [thread overview]
Message-ID: <981484.56.1284995756178.JavaMail.sprabhu@dhcp-1-233.fab.redhat.com> (raw)
In-Reply-To: <14128115.54.1284995685991.JavaMail.sprabhu@dhcp-1-233.fab.redhat.com>
----- "Chuck Lever" <chuck.lever@oracle.com> wrote:
> It also seems to me that if RHEL 4 is _not_ invalidating on lock, then
> it is not working as designed. AFAIK the Linux NFS client has always
> invalidated a file's data cache on lock. Did I misread something?
>
The flock support for NFS was only implemented in the 2.6.12 kernel. Hence on the RHEL 4 kernel ie 2.6.9 nfs_file_operations->flock is NULL and any flock operations performed by the application was only applicable on that node. No part of the NFS client code was executed for the flock() operation.
Sachin Prabhu
next parent reply other threads:[~2010-09-20 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14128115.54.1284995685991.JavaMail.sprabhu@dhcp-1-233.fab.redhat.com>
2010-09-20 15:15 ` Sachin Prabhu [this message]
2010-09-20 15:19 ` Should we be aggressively invalidating cache when using -onolock? Chuck Lever
2010-09-20 15:34 ` Sachin Prabhu
[not found] <1103741.22.1284726314119.JavaMail.sprabhu@dhcp-1-233.fab.redhat.com>
2010-09-17 12:26 ` Sachin Prabhu
2010-09-17 17:46 ` J. Bruce Fields
2010-09-18 11:09 ` Jeff Layton
2010-09-19 18:53 ` J. Bruce Fields
2010-09-20 14:41 ` Chuck Lever
2010-09-20 18:25 ` J. Bruce Fields
2010-10-05 14:27 ` Jeff Layton
2010-10-05 15:19 ` Suresh Jayaraman
[not found] ` <20101005102752.67b75416-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-20 10:42 ` Sachin Prabhu
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=981484.56.1284995756178.JavaMail.sprabhu@dhcp-1-233.fab.redhat.com \
--to=sprabhu@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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;
as well as URLs for NNTP newsgroup(s).