Lines Matching refs:netfs

14      may or may not have anything associated with it, but the netfs doesn't
17  (3) Barring the top-level index (one entry per cached netfs), the index
18      hierarchy for each netfs is structured according the whim of the netfs.
64  (1) The name of the netfs (used as the key in the toplevel index).
66  (2) The version of the netfs (if the name matches but the version doesn't, the
67      entire in-cache hierarchy for this netfs will be scrapped and begun
94 However, since it's unlikely that any two netfs's are going to want to define
97 the tree.  The netfs can even mix indices and data files at the same level, but
192  (4) A function to retrieve an object's key from the netfs [mandatory].
194      This function will be called with the netfs data that was passed to the
199  (5) A function to retrieve attribute data from the netfs [optional].
201      This function will be called with the netfs data that was passed to the
208  (6) A function to retrieve auxiliary data from the netfs [optional].
210      This function will be called with the netfs data that was passed to the
218      length.  A netfs mustn't rely on being able to provide more than 400 bytes
238      the cache and copy it into the netfs's structures.
257      information for this page and that the netfs should uncache the page when
287 	int fscache_register_netfs(struct fscache_netfs *netfs);
289 It just takes a pointer to the netfs definition.  It returns 0 or an error as
298 	void fscache_unregister_netfs(struct fscache_netfs *netfs);
353 This is all handled transparently, and the netfs doesn't see any of it.
452  (2) A read or allocated page must be uncached when the netfs page is released
463 Firstly, the netfs should ask FS-Cache to examine the caches and read the
498      (*) The netfs data supplied when the cookie was created.
550 Secondly, if the netfs changes the contents of the page (either due to an
658 might be holding for this netfs page.  This function must be called once for
689 This takes the netfs cookie, and the page and gfp arguments as supplied to
709 This takes the netfs cookie that the pages were cached with and the inode that
724 This will call back to the netfs to check whether the auxiliary data associated
806      This permits a netfs to request cache space be reserved to store up to the
856 Typically this will be necessary when the server tells the netfs of a foreign
857 change - at which point the netfs has to throw away all the state it had for an
874 Using the following function, the netfs can wait for the invalidation operation
890 to the netfs that the cache has an interest in this page, where an interest may
894 The netfs can use this information in methods such as releasepage() to