Lines Matching refs:writeback
2 * mm/page-writeback.c
22 #include <linux/writeback.h>
37 #include <trace/events/writeback.h>
41 * will look to see if it needs to force writeback or throttling.
47 * non-background writeback, this is how many pages it will attempt to write.
62 * Start background writeback (via writeback threads) at this percentage
79 * The generator of dirty data starts writeback at this percentage
116 * Scale the writeback cache size proportional to the relative writeout speeds.
119 * writeback completions [end_page_writeback()]. Those devices that write out
128 * measured in page writeback completions.
401 * global_dirty_limits - background-writeback and dirty-throttling thresholds
477 * the caller to perform writeback if the system is over `vm_dirty_ratio'.
478 * If we're over `background_thresh' then the writeback threads are woken to
509 * Throttle it only when the background writeback cannot
559 * Only move pages to writeback if this bdi is over its
622 * dirty state and will initiate writeback if needed.
713 * We've spun up the disk and we're in laptop mode: schedule writeback
724 * caused another writeback to be scheduled by laptop_io_completion.
725 * Nothing needs to be written back anymore, so we unschedule the writeback.
748 * thresholds before writeback cuts in.
779 * Called early on to tune the page writeback dirty limits.
817 * TOWRITE tag to identify pages eligible for writeback. This mechanism is
818 * used to avoid livelocking of writeback by a process steadily creating new
852 * if it's dirty. This is desirable behaviour for memory-cleaning writeback,
992 * we tagged for writeback prior to entering this loop.
1270 * cause the writeback.