Home
last modified time | relevance | path

Searched refs:for_sync (Results 1 – 3 of 3) sorted by relevance

/freebsd/sys/contrib/openzfs/module/os/linux/zfs/
H A Dzpl_file.c155 * we do need for_sync so that the pages remain in writeback until in zpl_fsync()
159 int for_sync = 1; in zpl_fsync() local
167 zpl_write_cache_pages(inode->i_mapping, &wbc, &for_sync); in zpl_fsync()
556 boolean_t *for_sync = data; in zpl_putpage() local
564 ret = zfs_putpage(pp->mapping->host, pp, wbc, *for_sync); in zpl_putpage()
687 boolean_t for_sync = (sync_mode == WB_SYNC_ALL); in zpl_writepages() local
689 result = zpl_write_cache_pages(mapping, wbc, &for_sync); in zpl_writepages()
724 result = zpl_write_cache_pages(mapping, wbc, &for_sync); in zpl_writepages()
742 boolean_t for_sync = (wbc->sync_mode == WB_SYNC_ALL); in zpl_writepage() local
744 return (zpl_putpage(pp, wbc, &for_sync)); in zpl_writepage()
[all...]
H A Dzfs_vnops_os.c3816 * for_sync - does the caller intend to wait synchronously for the in zfs_putpage()
3827 boolean_t for_sync) in zfs_putpage()
3970 return (for_sync ? err : 0); in zfs_putpage()
3996 * A note about for_sync vs wbc->sync_mode. in zfs_putpage()
3998 * for_sync indicates that this is a syncing writeback, that is, kernel in zfs_putpage()
4001 * op (eg fsync(), msync(MS_SYNC)). For our purposes, for_sync==TRUE in zfs_putpage()
4016 * So, why a separate for_sync field? This is because zpl_writepages() in zfs_putpage()
4018 * It wants all the individual pages to be for_sync==TRUE ie only in zfs_putpage()
4026 * for_sync: 0=unlock immediately; 1=unlock once on disk in zfs_putpage()
4032 * We use for_sync a in zfs_putpage()
3814 zfs_putpage(struct inode * ip,struct page * pp,struct writeback_control * wbc,boolean_t for_sync) zfs_putpage() argument
[all...]
/freebsd/sys/contrib/openzfs/include/os/linux/zfs/sys/
H A Dzfs_vnops_os.h66 struct writeback_control *wbc, boolean_t for_sync);