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;
92 * We need to consider the number of dirty buckets as well
95 * when very few dirty sectors consumed a lot dirty buckets, the
96 * worst case is when dirty buckets reached cutoff_writeback_sync and
97 * dirty data is still not even reached to writeback percent, so the rate
106 c->gc_stats.in_use > BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW && dirty > 0) {
108 div_s64((dirty_buckets * c->cache->sb.bucket_size), dirty);
122 fps = div_s64(dirty, dirty_buckets) * fp_term;
201 * In order to avoid extra locking cost for counting exact dirty cached
430 * IO errors are signalled using the dirty bit on the key.
460 "reading dirty data from cache");
594 /* Scan for dirty data */
753 * to perform writeback. Otherwise, if no dirty data on cache,
754 * or there is dirty data on cache but writeback is disabled,
782 * writeback thread should stop after there is no dirty
801 * When dirty data rate is high (e.g. 50%+), there might
891 pr_warn("sectors dirty init failed, ret=%d!\n", ret);