Searched refs:writepage (Results 1 – 25 of 55) sorted by relevance
123
| /Linux-v5.4/Documentation/filesystems/ |
| D | locking.rst | 238 int (*writepage)(struct page *page, struct writeback_control *wbc);
270 writepage: yes, unlocks (see below)
301 ->writepage() is used for two purposes: for "memory cleansing" and for
305 If writepage is called for sync (wbc->sync_mode != WBC_SYNC_NONE) then
309 If writepage is called for memory cleansing (sync_mode ==
311 possible. So writepage should try to avoid blocking against
324 caller, unless ->writepage() returns special WRITEPAGE_ACTIVATE
326 currently, and VM should stop calling ->writepage() on this page for some
331 and return zero, writepage *must* run set_page_writeback() against the page,
336 writepage.
[all …]
|
| D | vfs.rst | 603 in order to reuse them. To do this it can call the ->writepage method
618 ->writepage on. If mpage_writepages is not used (i.e. the address
642 set_page_dirty to write data into the address_space, and writepage and
649 typically remains set until writepage asks for it to be written. This
655 operations. This gives the the writepage and writepages operations some
658 return information back to the caller about the result of a writepage or
705 int (*writepage)(struct page *page, struct writeback_control *wbc);
738 ``writepage``
743 PageLocked is true. writepage should start writeout, should set
748 If wbc->sync_mode is WB_SYNC_NONE, ->writepage doesn't have to
[all …]
|
| /Linux-v5.4/fs/gfs2/ |
| D | meta_io.c | 92 .writepage = gfs2_aspace_writepage,
97 .writepage = gfs2_aspace_writepage,
|
| D | aops.c | 830 .writepage = gfs2_writepage,
844 .writepage = gfs2_jdata_writepage,
|
| /Linux-v5.4/fs/bfs/ |
| D | file.c | 192 .writepage = bfs_writepage,
|
| /Linux-v5.4/mm/ |
| D | page-writeback.c | 2159 struct writeback_control *wbc, writepage_t writepage, in write_cache_pages() argument
2238 error = (*writepage)(page, wbc, data); in write_cache_pages()
2303 int ret = mapping->a_ops->writepage(page, wbc); in __writepage()
2325 if (!mapping->a_ops->writepage) in generic_writepages()
2381 ret = mapping->a_ops->writepage(page, &wbc); in write_one_page()
|
| D | swap_state.c | 32 .writepage = swap_writepage,
|
| /Linux-v5.4/fs/9p/ |
| D | vfs_addr.c | 329 .writepage = v9fs_vfs_writepage,
|
| /Linux-v5.4/include/linux/ |
| D | writeback.h | 399 struct writeback_control *wbc, writepage_t writepage,
|
| /Linux-v5.4/fs/hpfs/ |
| D | file.c | 200 .writepage = hpfs_writepage,
|
| /Linux-v5.4/fs/udf/ |
| D | file.c | 130 .writepage = udf_adinicb_writepage,
|
| /Linux-v5.4/fs/adfs/ |
| D | inode.c | 76 .writepage = adfs_writepage,
|
| /Linux-v5.4/fs/hfsplus/ |
| D | inode.c | 159 .writepage = hfsplus_writepage,
168 .writepage = hfsplus_writepage,
|
| /Linux-v5.4/fs/hfs/ |
| D | inode.c | 162 .writepage = hfs_writepage,
171 .writepage = hfs_writepage,
|
| /Linux-v5.4/fs/ntfs/ |
| D | aops.c | 1658 .writepage = ntfs_writepage,
1673 .writepage = ntfs_writepage,
1688 .writepage = ntfs_writepage, /* Write dirty page to disk. */
|
| /Linux-v5.4/fs/jfs/ |
| D | inode.c | 362 .writepage = jfs_writepage,
|
| /Linux-v5.4/fs/omfs/ |
| D | file.c | 377 .writepage = omfs_writepage,
|
| /Linux-v5.4/fs/ecryptfs/ |
| D | mmap.c | 540 .writepage = ecryptfs_writepage,
|
| /Linux-v5.4/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_shmem.c | 263 ret = mapping->a_ops->writepage(page, &wbc); in shmem_writeback()
|
| /Linux-v5.4/fs/nilfs2/ |
| D | mdt.c | 437 .writepage = nilfs_mdt_write_page,
|
| /Linux-v5.4/fs/sysv/ |
| D | itree.c | 499 .writepage = sysv_writepage,
|
| /Linux-v5.4/fs/afs/ |
| D | file.c | 57 .writepage = afs_writepage,
|
| /Linux-v5.4/fs/ |
| D | mpage.c | 678 ret = mapping->a_ops->writepage(page, wbc); in __mpage_writepage()
|
| /Linux-v5.4/fs/nfs/ |
| D | file.c | 510 .writepage = nfs_writepage,
|
| /Linux-v5.4/drivers/staging/wlan-ng/ |
| D | hfa384x_usb.c | 1815 u16 writepage; in hfa384x_drvr_flashdl_write() local
1879 writepage = HFA384x_ADDR_CMD_MKPAGE(dlbufaddr + in hfa384x_drvr_flashdl_write()
1889 writepage, in hfa384x_drvr_flashdl_write()
|
123
