summaryrefslogtreecommitdiffstats
path: root/sys/nfs/nfs_serv.c
diff options
context:
space:
mode:
authormsmith <msmith@FreeBSD.org>1999-07-31 01:51:58 +0000
committermsmith <msmith@FreeBSD.org>1999-07-31 01:51:58 +0000
commit8d698b77fdf8dd6e4606832120dbd7c8062c1851 (patch)
treeacdca4d580e43ba470c3a0d405d605267c44d447 /sys/nfs/nfs_serv.c
parent599ae0bd07ffb710182a49dfbe878ce5fb011238 (diff)
downloadFreeBSD-src-8d698b77fdf8dd6e4606832120dbd7c8062c1851.zip
FreeBSD-src-8d698b77fdf8dd6e4606832120dbd7c8062c1851.tar.gz
As described by the submitter:
I did some tcpdumping the other day and noticed that GETATTR calls were frequently followed by an ACCESS call to the same file. The attached patch changes nfs_getattr to fill the access cache as a side effect. This is accomplished by calling ACCESS rather than GETATTR. This implies a modest overhead of 4 bytes in the request and 8 bytes in the response compared to doing a vanilla GETATTR. ... [The patch comprises two parts] The first is the "real" patch, the second counts misses and hits rather than fills and hits. The difference is subtle but important because both nfs_getattr and nfs_access now fill the cache. It also changes the default value of nfsaccess_cache_timeout to better match the attribute cache. IMHO, file timestamps change much more frequently than protection bits. Submitted by: Bjoern Groenvall <bg@sics.se> Reviewed by: dillon (partially)
Diffstat (limited to 'sys/nfs/nfs_serv.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud