Lines Matching defs:dirty
3 * background writeback - scan btree for dirty data and write it to the backing
42 * Unfortunately there is no control of global dirty data. If the
43 * user states that they want 10% dirty data in the cache, and has,
45 * backing volume uses about 2% of the cache for dirty data.
54 /* Ensure each backing dev gets at least one dirty share */
67 * First, the error (number of sectors that are dirty beyond our
75 * attempts to write at a rate that would retire all the dirty
84 int64_t dirty = bcache_dev_sectors_dirty(&dc->disk);
85 int64_t error = dirty - target;
163 * In order to avoid extra locking cost for counting exact dirty cached
384 * IO errors are signalled using the dirty bit on the key.
414 "reading dirty data from cache");
549 /* Scan for dirty data */
705 * to perform writeback. Otherwise, if no dirty data on cache,
706 * or there is dirty data on cache but writeback is disabled,
734 * writeback thread should stop after there is no dirty
744 * When dirty data rate is high (e.g. 50%+), there might
835 pr_warn("sectors dirty init failed, ret=%d!\n", ret);