Lines Matching full:that

12 applications that access a filesystem via a remote filesystem protocol
35 tree.  This means that if any filesystem object is in the dcache, then
36 all of the ancestors of that filesystem object are also in the dcache.
44 the dcache that are not needed for normal filesystem access.
46 1. The dcache must sometimes contain objects that are not part of the
47    proper prefix. i.e that are not connected to the root.
50    that dentry into place (based on the parent and name in the
52    it is a dcache invariant that directories only have one dentry.
57    any dentry that might not be part of the proper prefix.
62    kept in the dcache.  If a dentry that is not already in the dcache
67    Note that such a dentry can acquire children, name, ancestors, etc.
68    without losing DCACHE_DISCONNECTED - that flag is only cleared when
72    dentries.  That guarantees that we won't need to hunt them down upon
89       In the case of a directory, care is taken that only one dentry
104    2. make sure that d_splice_alias is used rather than d_add
120 A file system implementation declares that instances of the filesystem
142     so any filehandle lookup that requires finding a parent will fail.
156     export_operations struct also includes a flags field that allows the
162 The decode_fh routine should not depend on the stated size that is
172 contains a "flags" field that allows the filesystem to communicate to nfsd
173 that it may want to do things differently when dealing with it. The
177     RFC 1813 recommends that servers always send weak cache consistency
181     skip issuing GETATTRs in some situations but means that the server
183     (particularly those that are clustered or networked) this is expensive
185     that it should skip providing WCC attributes to the client in NFSv3
187     this on filesystems that have an expensive ->getattr inode operation,
193     vet to ensure that they live inside of an exported tree. When the
195     ensure that the filehandle live on the filesystem. When only part of a
197     inode to ensure that it's within an exported subtree. This is an
204     On some exportable filesystems (such as NFS) unlinking a file that
206     the NFS client will do a "sillyrename" to ensure that the file
207     sticks around while it's still open. When reexporting, that open
213     calling into the vfs to do an unlink or a rename that would replace
220     of dirty pages so that dirty pages for the client bdi do not imact
227     EXPORT_OP_NOATOMIC_ATTR indicates that the exported filesystem
238     all of an inode's dirty data on last close. Exports that behave this
239     way should set EXPORT_OP_FLUSH_ON_CLOSE so that NFSD knows to skip