Konstantin Belousov 6c21f6edb8 The VOP_LOOKUP() implementations for CREATE op do not put the name ... into namecache, to avoid cache trashing when doing large operations. E.g., tar archive extraction is not usually followed by access to many of the files created. Right now, each VOP_LOOKUP() implementation explicitely knowns about this quirk and tests for both MAKEENTRY flag presence and op != CREATE to make the call to cache_enter(). Centralize the handling of the quirk into VFS, by deciding to cache only by MAKEENTRY flag in VOP. VFS now sets NOCACHE flag for CREATE namei() calls. Note that the change in semantic is backward-compatible and could be merged to the stable branch, and is compatible with non-changed third-party filesystems which correctly handle MAKEENTRY. Suggested by: Chris Torek <torek@pi-coral.com> Reviewed by: mckusick Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 2 weeks		2014-12-18 10:01:12 +00:00
..
nfs_bio.c	Avoid an exclusive acquisition of the object lock on the expected execution	2014-09-14 18:07:55 +00:00
nfs_kdtrace.c
nfs_krpc.c
nfs_nfsiod.c
nfs_node.c
nfs_subs.c
nfs_vfsops.c	Follow up to r225617. In order to maximize the re-usability of kernel code	2014-10-16 18:04:43 +00:00
nfs_vnops.c	The VOP_LOOKUP() implementations for CREATE op do not put the name	2014-12-18 10:01:12 +00:00
nfs.h
nfsargs.h
nfsm_subs.h
nfsmount.h
nfsnode.h
nfsstats.h
nlminfo.h