summaryrefslogtreecommitdiffstats
path: root/include/linux/nfs_xdr.h
diff options
context:
space:
mode:
authorChuck Lever <cel@netapp.com>2005-10-25 11:48:36 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2005-10-27 22:12:40 -0400
commit0c70b50150cfb0b43ff500a8a394a52b4d5f1350 (patch)
tree292d31ce5378edb856076d2c610c323b76af0b09 /include/linux/nfs_xdr.h
parentdecf491f3076190262d4c649bed877650623903a (diff)
downloadop-kernel-dev-0c70b50150cfb0b43ff500a8a394a52b4d5f1350.zip
op-kernel-dev-0c70b50150cfb0b43ff500a8a394a52b4d5f1350.tar.gz
NFS: nfs_lookup doesn't need to revalidate the parent directory's inode
nfs_lookup() used to consult a lookup cache before trying an actual wire lookup operation. The lookup cache would be invalid, of course, if the parent directory's mtime had changed, so nfs_lookup performed an inode revalidation on the parent. Since nfs_lookup() doesn't use a cache anymore, the revalidation is no longer necessary. There are cases where it will generate a lot of unnecessary GETATTR traffic. See http://bugzilla.linux-nfs.org/show_bug.cgi?id=9 Test-plan: Use lndir and "rm -rf" and watch for excess GETATTR traffic or application level errors. Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'include/linux/nfs_xdr.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud