| /openbmc/linux/mm/ |
| H A D | show_mem.c | 35 unsigned long pagecache; in si_mem_available() local
59 pagecache = pages[LRU_ACTIVE_FILE] + pages[LRU_INACTIVE_FILE]; in si_mem_available()
60 pagecache -= min(pagecache / 2, wmark_low); in si_mem_available()
61 available += pagecache; in si_mem_available()
|
| H A D | Kconfig | 929 pagecache and when a subsystem requests for contiguous area, the
|
| /openbmc/qemu/block/ |
| H A D | nfs.c | 66 int64_t uid, gid, tcp_syncnt, readahead, pagecache, debug; member
492 client->pagecache = opts->page_cache_size; in nfs_client_open()
493 if (client->pagecache > QEMU_NFS_MAX_PAGECACHE_SIZE) { in nfs_client_open()
496 client->pagecache = QEMU_NFS_MAX_PAGECACHE_SIZE; in nfs_client_open()
498 nfs_set_pagecache(client->context, client->pagecache); in nfs_client_open()
|
| /openbmc/linux/Documentation/translations/zh_TW/process/ |
| H A D | coding-style.rst | 777 因爲體積大內核會占用更多的指令高速緩存，而且會導致 pagecache 的可用內存減少。
778 想像一下，一次 pagecache 未命中就會導致一次磁碟尋址，將耗時 5 毫秒。5 毫秒的
|
| /openbmc/linux/drivers/mtd/nand/raw/ |
| H A D | nand_base.c | 470 if (page == chip->pagecache.page) in nand_do_write_oob()
471 chip->pagecache.page = -1; in nand_do_write_oob()
3633 chip->pagecache.page = -1; in nand_do_read_ops()
3645 chip->pagecache.page = realpage; in nand_do_read_ops()
3646 chip->pagecache.bitflips = ret; in nand_do_read_ops()
3649 chip->pagecache.page = -1; in nand_do_read_ops()
3689 chip->pagecache.bitflips); in nand_do_read_ops()
4466 chip->pagecache.page = -1; in nand_do_write_ops()
4692 if (page <= chip->pagecache.page && chip->pagecache.page < in nand_erase_nand()
4694 chip->pagecache.page = -1; in nand_erase_nand()
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/process/ |
| H A D | coding-style.rst | 859 因为体积大内核会占用更多的指令高速缓存，而且会导致 pagecache 的可用内存减少。
860 想象一下，一次 pagecache 未命中就会导致一次磁盘寻址，将耗时 5 毫秒。5 毫秒的
|
| /openbmc/linux/include/linux/mtd/ |
| H A D | rawnand.h | 1311 } pagecache; member
1623 chip->pagecache.page = -1; in nand_get_data_buf()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 551 pages have been read into the pagecache. (See `Verifying data`_.)
632 For filesystems using Linux's pagecache, the ``->read_folio()`` and
638 which verifies data that has been read into the pagecache of a verity
646 as per the usual Linux pagecache behavior, attempts by userspace to
667 the pagecache, so the above subsection applies too. However, they
849 pagecache, but both local and remote filesystems normally do so.
|
| H A 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
929 The filesystem must return the locked pagecache page for the
951 'copied') that were able to be copied into pagecache.
1021 Called by the VM when reading a file through the pagecache when
|
| H A 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
|
| H A D | proc.rst | 1044 pagecache) as well as tmpfs & shmem.
1065 for the pagecache. The kernel must use tricks to access
1735 pagecache).
1787 by truncating pagecache. A task can cause "negative" IO too. If this task
1788 truncates some dirty pagecache, some IO which another task has been accounted
|
| H A D | locking.rst | 391 the pagecache will assume that private data is buffer_heads and call
|
| H A D | fscrypt.rst | 36 caching both the decrypted and encrypted pages in the pagecache,
1165 Note that mmap *is* supported. This is possible because the pagecache
|
| H A D | xfs-online-fsck-design.rst | 1938 tmpfs can only push a pagecache folio to the swap cache if the folio is neither
1941 Short term direct access to xfile contents is done by locking the pagecache
|
| /openbmc/linux/Documentation/filesystems/caching/ |
| H A 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
|
| /openbmc/linux/Documentation/core-api/ |
| H A 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.
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | vm.rst | 234 To free pagecache::
242 To free slab objects and pagecache::
253 (inodes, dentries, pagecache, etc...) These objects are automatically
958 reclaim dentries and inodes at a "fair" rate with respect to pagecache and
|
| /openbmc/linux/fs/ |
| H A D | Kconfig | 65 then you can avoid using the pagecache to buffer I/Os. Turning
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 25 KSM only merges anonymous (private) pages, never pagecache (file) pages.
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kfence.rst | 293 limits frequent long-lived allocations (e.g. pagecache) of the same source
|
| /openbmc/linux/fs/befs/ |
| H A D | ChangeLog | 206 * Made it an option to use the old non-pagecache befs_file_read() for
|
| /openbmc/linux/Documentation/process/ |
| H A D | coding-style.rst | 967 available for the pagecache. Just think about it; a pagecache miss causes a
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-block | 223 pagecache. It shows '1' if true, '0' if not.
|
| /openbmc/linux/Documentation/admin-guide/cifs/ |
| H A D | usage.rst | 517 (writebehind) through the local Linux client pagecache
|
| /openbmc/linux/Documentation/translations/sp_SP/process/ |
| H A D | coding-style.rst | 999 para el pagecache. Solo piense en esto; un fallo en la memoria caché de la
|