Lines Matching defs:writeback
3 * fs/fs-writeback.c
9 * pages against inodes. ie: data writeback. Writeout of the
14 * Additions for address_space-based writeback
26 #include <linux/writeback.h>
50 unsigned int for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
52 enum wb_reason reason; /* why was writeback initiated? */
81 #include <trace/events/writeback.h>
222 * The current cgroup writeback is built on the assumption that multiple
403 * pages actually under writeback.
560 * Record @inode's writeback context into @wbc and unlock the i_lock. On
561 * writeback completion, wbc_detach_inode() should be called. This is used
562 * to track the cgroup writeback context.
599 * @wbc: writeback_control of the just finished writeback
601 * To be called after a writeback attempt of an inode finishes and undoes
606 * the usefulness of such sharing, cgroup writeback tracks ownership
611 * behaviors (single foreign page can lead to gigabytes of writeback to be
614 * To resolve this issue, cgroup writeback detects the majority dirtier of
618 * a certain amount of time and/or writeback attempts.
620 * On each writeback attempt, @wbc tries to detect the majority writer
721 * wbc_account_cgroup_owner - account writeback to update inode cgroup ownership
722 * @wbc: writeback_control of the writeback in progress
726 * @bytes from @page are about to written out during the writeback
740 * regular writeback instead of writing things out itself.
778 * If cgroup writeback is enabled for @inode, the congestion state is
839 * @skip_if_busy: skip wb's which already have writeback in progress
918 * cgroup_writeback_by_id - initiate cgroup writeback from bdi and memcg IDs
922 * @reason: reason why some writeback work initiated
970 unsigned long filepages, headroom, dirty, writeback;
973 &writeback);
977 /* issue the writeback work */
1092 * All callers of this function want to start writeback of all
1108 * wb_start_background_writeback - start background writeback
1112 * This makes sure WB_SYNC_NONE background writeback happens. When
1121 * writeback as soon as there is no other work to do.
1128 * Remove the inode from the writeback list it is on.
1143 * mark an inode as under writeback on the sb
1161 * clear an inode as under writeback on the sb
1235 * from permanently stopping the whole bdi writeback.
1337 * Wait for writeback on an inode to complete. Called with i_lock held.
1357 * Wait for writeback on an inode to complete. Caller must have inode pinned.
1387 * Find proper writeback list for the inode depending on its current state and
1388 * possibly also change of its state while we were doing writeback. Here we
1389 * handle things such as livelock prevention or fairness of writeback among
1391 * processes all inodes in writeback lists and requeueing inodes behind flusher
1411 * writeback is not making progress due to locked
1431 * retrying writeback of the dirty page/inode
1438 * Filesystems can dirty the inode during writeback operations,
1448 /* The inode is clean. Remove from writeback lists. */
1454 * Write out an inode and its dirty pages. Do not update the writeback list
1475 * I/O completion. We don't do it for sync(2) writeback because it has a
1499 * Some filesystems may redirty the inode during the writeback
1541 * and does more profound writeback list handling in writeback_sb_inodes().
1567 * Skip inode if it is clean and we have no outstanding writeback in
1568 * WB_SYNC_ALL mode. We don't want to mess with writeback lists in this
1571 * make sure inode is on some writeback list and leave it there unless
1588 * If inode is clean, remove it from writeback lists. Otherwise don't
1610 * The intended call sequence for WB_SYNC_ALL writeback is:
1695 * If this inode is locked for writeback and we are not
1696 * doing writeback-for-data-integrity, move it to
1697 * b_more_io so that writeback can proceed with the
1712 * are doing WB_SYNC_NONE writeback. So this catches only the
1842 * Explicit flushing or periodic writeback of "old" data.
1845 * dirtying-time in the inode's address_space. So this periodic writeback code
1849 * Try to run once per dirty_writeback_interval. But if a writeback event
1870 * Stop writeback when nr_pages has been consumed
1876 * Background writeout and kupdate-style writeback may
1918 * Dirty inodes are moved to b_io for writeback in batches.
1932 * become available for writeback. Otherwise
1990 * When set to zero, disable periodic writeback
2043 * Retrieve work items and do the writeback they describe
2063 * Check for periodic writeback, kupdated() style
2073 * Handle writeback of dirty data for the device backed by this bdi. Also
2117 * Start writeback of `nr_pages' pages on this bdi. If `nr_pages' is zero,
2141 * Wakeup the flusher threads to start writeback of all currently dirty pages
2148 * If we are expecting writeback progress we must submit plugged IO.
2283 * If the inode is queued for writeback by flush worker, just
2367 * Splice the writeback list onto a temporary list to avoid waiting on
2368 * inodes that have started writeback after this point.
2372 * the local list because inodes can be dropped from either by writeback
2380 * Data integrity sync. Must wait for all pages under writeback, because
2394 * writeback tag. Writeback completion is responsible to remove
2395 * the inode from either list once the writeback tag is cleared.
2422 * applications can catch the writeback error using fsync(2).
2462 * writeback_inodes_sb_nr - writeback dirty inodes from given super_block
2465 * @reason: reason why some writeback work initiated
2467 * Start writeback on some inodes on this super_block. No guarantees are made
2480 * writeback_inodes_sb - writeback dirty inodes from given super_block
2482 * @reason: reason why some writeback work was initiated
2484 * Start writeback on some inodes on this super_block. No guarantees are made
2495 * try_to_writeback_inodes_sb - try to start writeback if none underway
2497 * @reason: reason why some writeback work was initiated
2499 * Invoke __writeback_inodes_sb_nr if no writeback is currently underway.
2534 * inodes under writeback and I_DIRTY_TIME inodes ignored by
2581 * @wbc: controls the writeback mode