Searched refs:netfs (Results 1 – 12 of 12) sorted by relevance
/kernel/linux/linux-5.10/fs/fscache/ |
D | netfs.c | 16 int __fscache_register_netfs(struct fscache_netfs *netfs) in __fscache_register_netfs() argument 20 _enter("{%s}", netfs->name); in __fscache_register_netfs() 25 netfs->name, strlen(netfs->name), in __fscache_register_netfs() 26 &netfs->version, sizeof(netfs->version), in __fscache_register_netfs() 27 netfs, 0); in __fscache_register_netfs() 47 netfs->primary_index = cookie; in __fscache_register_netfs() 49 pr_notice("Netfs '%s' registered for caching\n", netfs->name); in __fscache_register_netfs() 50 trace_fscache_netfs(netfs); in __fscache_register_netfs() 65 void __fscache_unregister_netfs(struct fscache_netfs *netfs) in __fscache_unregister_netfs() argument 67 _enter("{%s.%u}", netfs->name, netfs->version); in __fscache_unregister_netfs() [all …]
|
D | fsdef.c | 79 struct fscache_netfs *netfs = cookie_netfs_data; in fscache_fsdef_netfs_check_aux() local 82 _enter("{%s},,%hu", netfs->name, datalen); in fscache_fsdef_netfs_check_aux() 90 if (version != netfs->version) { in fscache_fsdef_netfs_check_aux() 91 _leave(" = OBSOLETE [ver=%x net=%x]", version, netfs->version); in fscache_fsdef_netfs_check_aux()
|
D | Makefile | 11 netfs.o \
|
/kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
D | object.rst | 26 FS-Cache maintains an in-kernel representation of each object that a netfs is 88 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) 182 At the completion of lookup, FS-Cache will let the netfs go ahead with 200 operations the netfs has queued for an object. If creation failed, the 205 servicing netfs requests: 215 The normal running state. In this state, requests the netfs makes will be 228 netfs's records. This involves updating the auxiliary data that is used [all …]
|
D | fscache.rst | 71 FS-Cache does not follow the idea of completely loading every netfs file 73 then serving the pages out of that cache rather than the netfs inode because: 88 the netfs('s) using it. 98 (3) The netfs is provided with an interface that allows either party to 101 (4) The interface to the netfs returns as few errors as possible, preferring 102 rather to let the netfs remain oblivious. 105 netfs. The simplest cookie is just a NULL pointer - indicating nothing 108 (6) The netfs is allowed to propose - dynamically - any index hierarchy it 113 (7) Data I/O is done direct to and from the netfs's pages. The netfs 116 not start I/O on that page, but if it does, a netfs callback will be [all …]
|
D | backend-api.rst | 78 (1) that of the userspace process that issued the netfs operation that caused 109 struct fscache_netfs *netfs; 115 definition, the netfs definition and the netfs's data for this cookie. 116 The object definition contain functions supplied by the netfs for loading 183 allocation requests made by the netfs. This struct is then passed to the 255 object is found to exist and the netfs indicates that it is valid then 305 the object against the netfs's idea of the state. 0 should be returned 366 * Notification that the attributes on a netfs file changed [mandatory]:: 370 This is called to indicate to the cache that certain attributes on a netfs 372 cache can read these from the netfs by calling the cookie's get_attr() [all …]
|
D | netfs-api.rst | 16 may or may not have anything associated with it, but the netfs doesn't 19 (3) Barring the top-level index (one entry per cached netfs), the index 20 hierarchy for each netfs is structured according the whim of the netfs. 65 (1) The name of the netfs (used as the key in the toplevel index). 67 (2) The version of the netfs (if the name matches but the version doesn't, the 68 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 201 the cache and copy it into the netfs's structures. 220 information for this page and that the netfs should uncache the page when [all …]
|
D | index.rst | 13 netfs-api
|
D | operations.rst | 84 synchronously - and the netfs does not proceed until this has been 100 page to a netfs page after the backing fs has read the page in.
|
D | cachefiles.rst | 283 the netfs. The latter is used to detect stale objects in the cache and update 396 process issued the original syscall on the netfs.
|
/kernel/linux/linux-5.10/include/linux/ |
D | fscache.h | 240 int fscache_register_netfs(struct fscache_netfs *netfs) in fscache_register_netfs() argument 243 return __fscache_register_netfs(netfs); in fscache_register_netfs() 260 void fscache_unregister_netfs(struct fscache_netfs *netfs) in fscache_unregister_netfs() argument 263 __fscache_unregister_netfs(netfs); in fscache_unregister_netfs()
|
/kernel/linux/linux-5.10/include/trace/events/ |
D | fscache.h | 197 TP_PROTO(struct fscache_netfs *netfs), 199 TP_ARGS(netfs), 207 __entry->cookie = netfs->primary_index; 208 strncpy(__entry->name, netfs->name, 8);
|