From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Chow <davidchow@shaolinmicro.com>
Subject: Problems of lookup_revalidate
Date: Mon, 26 Aug 2002 23:53:22 +0800
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <3D6A4EF2.1070607@shaolinmicro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-fsdevel-owner@vger.kernel.org>
To: trond.myklebust@fys.uio.no, linux-fsdevel@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Trond,

I think the strategy used in 2.4.19 for NFS dentry and inode updates are 
too weak. May be you have being pushing too hard on optimizing 
performance (fewer lookups and revalidate). But I have problems that the 
client d_cache() inconsistency. It seems when the server changes file 
mode or ownership, the client is not updated properly unless I explicity 
add a file in the parent directory at the server which triggers the 
mtime of the parent, the client hardly update the dcache and inode 
parameters properly. Please clarify if my guess is wrong. Thanks.

David