writeback: move global_dirty_limit into wb_domain
This patch is a part of the series to define wb_domain which represents a domain that wb's (bdi_writeback's) belong to and are measured against each other in. This will enable IO backpressure propagation for cgroup writeback. global_dirty_limit exists to regulate the global dirty threshold which is a property of the wb_domain. This patch moves hard_dirty_limit, dirty_lock, and update_time into wb_domain. This is pure reorganization and doesn't introduce any behavioral changes. Signed-off-by: Tejun Heo <tj@kernel.org> Cc: Jens Axboe <axboe@kernel.dk> Cc: Jan Kara <jack@suse.cz> Cc: Wu Fengguang <fengguang.wu@intel.com> Cc: Greg Thelen <gthelen@google.com> Signed-off-by: Jens Axboe <axboe@fb.com>
This commit is contained in:
@@ -887,7 +887,7 @@ static long writeback_chunk_size(struct bdi_writeback *wb,
|
||||
pages = LONG_MAX;
|
||||
else {
|
||||
pages = min(wb->avg_write_bandwidth / 2,
|
||||
global_dirty_limit / DIRTY_SCOPE);
|
||||
global_wb_domain.dirty_limit / DIRTY_SCOPE);
|
||||
pages = min(pages, work->nr_pages);
|
||||
pages = round_down(pages + MIN_WRITEBACK_PAGES,
|
||||
MIN_WRITEBACK_PAGES);
|
||||
|
Reference in New Issue
Block a user