git://ftp.safe.ca / safe / jmp / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e323ea4) | patch
NFS: Don't force a dcache revalidation if nfs_wcc_update_inode succeeds
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Thu, 27 Sep 2007 14:07:31 +0000 (10:07 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 9 Oct 2007 21:18:55 +0000 (17:18 -0400)
commit17cadc95372e28024be0874e67329c1862912c5d
tree0785ba140643d87c23e7bca67d1f2522214a0d12tree | snapshot
parente323ea46d95d7f8c789effd1194dfc120284dbbdcommit | diff
NFS: Don't force a dcache revalidation if nfs_wcc_update_inode succeeds

The reason is that if the weak cache consistency update was successful,
then we know that our client must be the only one that changed the
directory, and we've already updated the dcache to reflect the change.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/inode.c diff | blob | history
fs/nfs/nfs4proc.c diff | blob | history
include/linux/nfs_fs.h diff | blob | history
Full containers within linux kernel