NFS: Fix the resolution problem with nfs_inode_attrs_need_update()
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 14 Oct 2008 23:16:07 +0000 (19:16 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 14 Oct 2008 23:23:17 +0000 (19:23 -0400)
commit4704f0e274829e3af00737d2d9adace2d71a9605
tree048404f927dc210f1d7c695cb39e28e4e7d49030
parent921615f111108258820226a3258a047d9bf1d96a
NFS: Fix the resolution problem with nfs_inode_attrs_need_update()

It appears that 'jiffies' timestamps do not have high enough resolution for
nfs_inode_attrs_need_update(). One problem is that a GETATTR can be
launched within < 1 jiffy of the last operation that updated the attribute.
Another problem is that RPC calls can take < 1 jiffy to execute.

We can fix this by switching the variables to use a simple global counter
that gets incremented every time we start another GETATTR call.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/dir.c
fs/nfs/inode.c
include/linux/nfs_fs.h
include/linux/nfs_xdr.h