| /linux-6.12.1/Documentation/filesystems/iomap/ |
| D | operations.rst | 24 File contents are cached in memory ("pagecache") to satisfy reads and
29 iomap implements nearly all the folio and pagecache management that
32 mapping, managing uptodate and dirty state, or writeback of pagecache
38 be used, which makes buffered I/O much more efficient, and the pagecache
63 The ``->iomap_begin`` function for pagecache operations may set the
87 - ``put_folio``: Called to unlock and put a folio after a pagecache
96 ``->iomap_begin`` and ``->iomap_end`` because pagecache operations
100 mapping for a particular pagecache folio can `change in the time it
105 For the pagecache, races can happen if writeback doesn't take
137 If the fsblock size matches the size of a pagecache folio, it is assumed
[all …]
|
| D | design.rst | 38 * Folio write faults to the pagecache
53 pagecache programmers and code reviewers.
83 So far only the pagecache operations need to do this.
117 * ``invalidate_lock``: The pagecache ``struct address_space``
140 writing the pagecache.
187 iomap does not support writing (whether via pagecache or direct
235 heads for pagecache operations.
260 Currently, these flags are only set by pagecache operations.
279 * ``folio_ops`` will be covered in the section on pagecache operations.
283 For pagecache operations this is critical for correct operation
[all …]
|
| D | porting.rst | 38 iomap handles common pagecache related operations itself, such as
114 For unjournalled filesystems that use the pagecache for symbolic links
|
| /linux-6.12.1/mm/ |
| D | show_mem.c | 35 unsigned long pagecache; in si_mem_available() local
54 pagecache = global_node_page_state(NR_ACTIVE_FILE) + in si_mem_available()
56 pagecache -= min(pagecache / 2, wmark_low); in si_mem_available()
57 available += pagecache; in si_mem_available()
|
| D | Kconfig | 935 pagecache and when a subsystem requests for contiguous area, the
|
| /linux-6.12.1/fs/bcachefs/ |
| D | Makefile | 49 fs-io-pagecache.o \
|
| /linux-6.12.1/drivers/mtd/nand/raw/ |
| D | nand_base.c | 473 if (page == chip->pagecache.page) in nand_do_write_oob()
474 chip->pagecache.page = -1; in nand_do_write_oob()
3623 if (realpage != chip->pagecache.page || oob) { in nand_do_read_ops()
3649 chip->pagecache.page = -1; in nand_do_read_ops()
3661 chip->pagecache.page = realpage; in nand_do_read_ops()
3662 chip->pagecache.bitflips = ret; in nand_do_read_ops()
3665 chip->pagecache.page = -1; in nand_do_read_ops()
3705 chip->pagecache.bitflips); in nand_do_read_ops()
4483 if (to <= ((loff_t)chip->pagecache.page << chip->page_shift) && in nand_do_write_ops()
4484 ((loff_t)chip->pagecache.page << chip->page_shift) < (to + ops->len)) in nand_do_write_ops()
[all …]
|
| /linux-6.12.1/Documentation/translations/zh_CN/process/ |
| D | coding-style.rst | 859 因为体积大内核会占用更多的指令高速缓存，而且会导致 pagecache 的可用内存减少。
860 想象一下，一次 pagecache 未命中就会导致一次磁盘寻址，将耗时 5 毫秒。5 毫秒的
|
| /linux-6.12.1/Documentation/translations/zh_TW/process/ |
| D | coding-style.rst | 862 因爲體積大內核會佔用更多的指令高速緩存，而且會導致 pagecache 的可用內存減少。
863 想象一下，一次 pagecache 未命中就會導致一次磁盤尋址，將耗時 5 毫秒。5 毫秒的
|
| /linux-6.12.1/include/linux/mtd/ |
| D | rawnand.h | 1324 } pagecache; member
1636 chip->pagecache.page = -1; in nand_get_data_buf()
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | fsverity.rst | 574 pages have been read into the pagecache. (See `Verifying data`_.)
655 For filesystems using Linux's pagecache, the ``->read_folio()`` and
661 which verifies data that has been read into the pagecache of a verity
669 as per the usual Linux pagecache behavior, attempts by userspace to
690 the pagecache, so the above subsection applies too. However, they
872 pagecache, but both local and remote filesystems normally do so.
|
| D | vfs.rst | 340 *not* evict the pagecache or inode-associated metadata buffers;
774 generic pagecache infrastructure does not track the file descriptions
788 occurs. Then, after writing back data from the pagecache in their
928 The filesystem must return the locked pagecache folio for the
950 'copied') that were able to be copied into pagecache.
1020 Called by the VM when reading a file through the pagecache when
|
| D | porting.rst | 336 remaining links or not. Caller does *not* evict the pagecache or inode-associated
625 its pagecache. No highmem pages should end up in the pagecache of such
|
| D | proc.rst | 1090 pagecache) as well as tmpfs & shmem.
1111 for the pagecache. The kernel must use tricks to access
1781 pagecache).
1833 by truncating pagecache. A task can cause "negative" IO too. If this task
1834 truncates some dirty pagecache, some IO which another task has been accounted
|
| D | locking.rst | 391 the pagecache will assume that private data is buffer_heads and call
|
| D | fscrypt.rst | 37 pagecache, thereby nearly halving the memory used and bringing it in
1223 Note that mmap *is* supported. This is possible because the pagecache
|
| /linux-6.12.1/Documentation/core-api/ |
| D | cachetlb.rst | 310 private". The kernel guarantees that, for pagecache pages, it will
311 clear this bit when such a page first enters the pagecache.
|
| /linux-6.12.1/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 78 pagecache becomes dirty and unuse it when writeback is complete. This is
215 pagecache in order to avoid an oops due to trying to open a file during process
|
| /linux-6.12.1/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 236 To free pagecache::
244 To free slab objects and pagecache::
255 (inodes, dentries, pagecache, etc...) These objects are automatically
1012 reclaim dentries and inodes at a "fair" rate with respect to pagecache and
|
| /linux-6.12.1/fs/ |
| D | Kconfig | 69 then you can avoid using the pagecache to buffer I/Os. Turning
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kfence.rst | 300 limits frequent long-lived allocations (e.g. pagecache) of the same source
|
| /linux-6.12.1/fs/befs/ |
| D | ChangeLog | 206 * Made it an option to use the old non-pagecache befs_file_read() for
|
| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | ksm.rst | 25 KSM only merges anonymous (private) pages, never pagecache (file) pages.
|
| /linux-6.12.1/Documentation/process/ |
| D | coding-style.rst | 983 available for the pagecache. Just think about it; a pagecache miss causes a
|
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-block | 276 pagecache. It shows '1' if true, '0' if not.
|