Searched refs:netfs (Results 1 – 10 of 10) sorted by relevance
| /linux-4.4.14/fs/fscache/ |
| D | netfs.c | 22 int __fscache_register_netfs(struct fscache_netfs *netfs) in __fscache_register_netfs() argument
28 _enter("{%s}", netfs->name); in __fscache_register_netfs()
30 INIT_LIST_HEAD(&netfs->link); in __fscache_register_netfs()
47 cookie->netfs_data = netfs; in __fscache_register_netfs()
58 if (strcmp(ptr->name, netfs->name) == 0) in __fscache_register_netfs()
65 netfs->primary_index = cookie; in __fscache_register_netfs()
66 list_add(&netfs->link, &fscache_netfs_list); in __fscache_register_netfs()
69 pr_notice("Netfs '%s' registered for caching\n", netfs->name); in __fscache_register_netfs()
86 void __fscache_unregister_netfs(struct fscache_netfs *netfs) in __fscache_unregister_netfs() argument
88 _enter("{%s.%u}", netfs->name, netfs->version); in __fscache_unregister_netfs()
[all …]
|
| D | fsdef.c | 86 const struct fscache_netfs *netfs = cookie_netfs_data; in fscache_fsdef_netfs_get_key() local
89 _enter("{%s.%u},", netfs->name, netfs->version); in fscache_fsdef_netfs_get_key()
91 klen = strlen(netfs->name); in fscache_fsdef_netfs_get_key()
95 memcpy(buffer, netfs->name, klen); in fscache_fsdef_netfs_get_key()
106 const struct fscache_netfs *netfs = cookie_netfs_data; in fscache_fsdef_netfs_get_aux() local
109 _enter("{%s.%u},", netfs->name, netfs->version); in fscache_fsdef_netfs_get_aux()
115 memcpy(buffer, &netfs->version, dlen); in fscache_fsdef_netfs_get_aux()
128 struct fscache_netfs *netfs = cookie_netfs_data; in fscache_fsdef_netfs_check_aux() local
131 _enter("{%s},,%hu", netfs->name, datalen); in fscache_fsdef_netfs_check_aux()
139 if (version != netfs->version) { in fscache_fsdef_netfs_check_aux()
[all …]
|
| D | Makefile | 10 netfs.o \
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 25 FS-Cache maintains an in-kernel representation of each object that a netfs is
87 As far as the netfs API goes, the netfs is only actually permitted to see
111 (3) Normal running: states that allow netfs operations on objects to proceed
114 (4) Termination: states that detach objects from their netfs cookies, that
149 to disconnecting the netfs's representation of a cache object (fscache_cookie)
183 At the completion of lookup, FS-Cache will let the netfs go ahead with
201 operations the netfs has queued for an object. If creation failed, the
206 servicing netfs requests:
216 The normal running state. In this state, requests the netfs makes will be
229 netfs's records. This involves updating the auxiliary data that is used
[all …]
|
| D | netfs-api.txt | 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
[all …]
|
| D | fscache.txt | 70 FS-Cache does not follow the idea of completely loading every netfs file
72 then serving the pages out of that cache rather than the netfs inode because:
87 the netfs('s) using it.
97 (3) The netfs is provided with an interface that allows either party to
100 (4) The interface to the netfs returns as few errors as possible, preferring
101 rather to let the netfs remain oblivious.
104 netfs. The simplest cookie is just a NULL pointer - indicating nothing
107 (6) The netfs is allowed to propose - dynamically - any index hierarchy it
112 (7) Data I/O is done direct to and from the netfs's pages. The netfs
115 not start I/O on that page, but if it does, a netfs callback will be
[all …]
|
| D | backend-api.txt | 79 (1) that of the userspace process that issued the netfs operation that caused
112 struct fscache_netfs *netfs;
118 definition, the netfs definition and the netfs's data for this cookie.
119 The object definition contain functions supplied by the netfs for loading
186 allocation requests made by the netfs. This struct is then passed to the
257 object is found to exist and the netfs indicates that it is valid then
307 the object against the netfs's idea of the state. 0 should be returned
368 (*) Notification that the attributes on a netfs file changed [mandatory]:
372 This is called to indicate to the cache that certain attributes on a netfs
374 cache can read these from the netfs by calling the cookie's get_attr()
[all …]
|
| D | operations.txt | 85 synchronously - and the netfs does not proceed until this has been
101 page to a netfs page after the backing fs has read the page in.
|
| D | cachefiles.txt | 302 the netfs. The latter is used to detect stale objects in the cache and update
417 process issued the original syscall on the netfs.
|
| /linux-4.4.14/include/linux/ |
| D | fscache.h | 264 int fscache_register_netfs(struct fscache_netfs *netfs) in fscache_register_netfs() argument
267 return __fscache_register_netfs(netfs); in fscache_register_netfs()
284 void fscache_unregister_netfs(struct fscache_netfs *netfs) in fscache_unregister_netfs() argument
287 __fscache_unregister_netfs(netfs); in fscache_unregister_netfs()
|