Searched refs:readpages (Results 1 – 10 of 10) sorted by relevance
| /Linux-v5.15/mm/ |
| D | readahead.c | 136 } else if (aops->readpages) { in read_pages()
137 aops->readpages(rac->file, rac->mapping, pages, in read_pages()
219 if (mapping->a_ops->readpages) { in page_cache_ra_unbounded()
284 if (unlikely(!mapping->a_ops->readpage && !mapping->a_ops->readpages && in force_page_cache_ra()
|
| /Linux-v5.15/Documentation/filesystems/caching/ |
| D | operations.rst | 81 This is, for example, used in read operations for calling readpages() on
82 the backing filesystem in CacheFiles. Although readpages() does an
|
| D | netfs-api.rst | 567 readpages() address space operation::
|
| /Linux-v5.15/fs/9p/ |
| D | vfs_addr.c | 331 .readpages = v9fs_vfs_readpages,
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | locking.rst | 249 int (*readpages)(struct file *filp, struct address_space *mapping,
282 readpages: no shared
308 ->readpages() populates the pagecache with the passed pages and starts
|
| D | fsverity.rst | 552 ``->readpages()`` methods must be modified to verify pages before they
614 Files on ext4 and f2fs may contain holes. Normally, ``->readpages()``
781 ``->readpages()``. Therefore, currently it's not possible for
|
| D | vfs.rst | 729 int (*readpages)(struct file *filp, struct address_space *mapping,
816 ``readpages``
820 readpages is only used for read-ahead, so read errors are
|
| /Linux-v5.15/fs/nfs/ |
| D | file.c | 518 .readpages = nfs_readpages,
|
| /Linux-v5.15/include/linux/ |
| D | fs.h | 386 int (*readpages)(struct file *filp, struct address_space *mapping, member
|
| /Linux-v5.15/fs/cifs/ |
| D | file.c | 4970 .readpages = cifs_readpages,
|
