mm: fix writeback regression for strictlimit BDIs
Subsystems (3)
PATCH 1/1 mm: fix writeback regression for strictlimit BDIs
Commit 64dd89ae01f2 ("mm/block/fs: remove laptop_mode") removed this unconditional writeback kick from balance_dirty_pages():
if (unlikely(!writeback_in_progress(wb))) wb_start_background_writeback(wb);
Earlier in balance_dirty_pages(), background writeback is started if the global dirty count exceeds the global background threshold (nr_dirty > gdtc->bg_thresh). However for BDIs with BDI_CAP_STRICTLIMIT set (eg fuse), throttling is calculated using the per-wb threshold, not global thresholds. This means the per-wb threshold can be exceeded while the global nr_dirty is below gdtc->bg_thresh. This causes two problems:
a) background writeback is never proactively kicked off. The flusher should be kicked off while the writer is still free-running, so that dirty pages are drained before the writer hits the throttle threshold. For strictlimit BDIs with global nr_dirty < gdtc->bg_thresh, this never kicks off the flusher, so dirty pages pile up unchecked until the per-wb freerun ceiling gets hit and IO is throttled
b) while IO is throttled, the flusher is still not started, which means the writer basically sits in the throttle loop sleeping while waiting for dirty pages to be cleaned but no writeback is running
This leads to severe stalls and degraded throughput. On fuse, buffered write performance drops from 1400 MiB/s to 2000 KiB/s.
This fixes the issue by kicking off the flusher if wb_dirty exceeds wb_bg_thresh for strictlimit BDIs. This restores performance back to its original baseline.
--- mm/page-writeback.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
mm/page-writeback.c +3 -1
@@ -1835,7 +1835,9 @@ static int balance_dirty_pages(struct bdi_writeback *wb,balance_domain_limits (mdtc, strictlimit); } -if (nr_dirty > gdtc->bg_thresh && !writeback_in_progress (wb)) +if (!writeback_in_progress (wb) && + (nr_dirty > gdtc->bg_thresh || + (strictlimit && gdtc->wb_dirty > gdtc->wb_bg_thresh)))wb_start_background_writeback (wb);/*
Signature · 1 line
2.52.0
Quoted 5 lines · Joanne Koong
Commit
64dd89ae01f2("mm/block/fs: removelaptop_mode") removed this unconditional writeback kick frombalance_dirty_pages():if (unlikely(!writeback_in_progress(wb))) wb_start_background_writeback(wb);
Yes, that looks like a bug.
Quoted 3 lines
This fixes the issue by kicking off the flusher if
wb_dirtyexceedswb_bg_threshfor strictlimit BDIs. This restores performance back to its original baseline.
What speaks against just reinstating the old-code as-is minus the misleading latop_mode comment?
Quoted 8 lines · Christoph Hellwig
Quoted 5 lines · Joanne Koong
Commit
64dd89ae01f2("mm/block/fs: removelaptop_mode") removed this unconditional writeback kick frombalance_dirty_pages():if (unlikely(!writeback_in_progress(wb))) wb_start_background_writeback(wb);
Quoted 9 lines
Yes, that looks like a bug.
Quoted 3 lines
This fixes the issue by kicking off the flusher if
wb_dirtyexceedswb_bg_threshfor strictlimit BDIs. This restores performance back to its original baseline.What speaks against just reinstating the old-code as-is minus the misleading
latop_modecomment?
I thought those two lines were unnecessary for nonstrictlimited bdis but after reading Jan's feedback, you're right this should just reinstate the old code as is.
Thanks,
Joanne
Jan Kara
maintainerQuoted 27 lines · Joanne Koong
Commit
64dd89ae01f2("mm/block/fs: removelaptop_mode") removed this unconditional writeback kick frombalance_dirty_pages():if (unlikely(!writeback_in_progress(wb))) wb_start_background_writeback(wb);Earlier in
balance_dirty_pages(), background writeback is started if the global dirty count exceeds the global background threshold (nr_dirty>gdtc->bg_thresh). However for BDIs withBDI_CAP_STRICTLIMITset (eg fuse), throttling is calculated using the per-wb threshold, not global thresholds. This means the per-wb threshold can be exceeded while the globalnr_dirtyis belowgdtc->bg_thresh. This causes two problems:a) background writeback is never proactively kicked off. The flusher should be kicked off while the writer is still free-running, so that dirty pages are drained before the writer hits the throttle threshold. For strictlimit BDIs with global
nr_dirty<gdtc->bg_thresh, this never kicks off the flusher, so dirty pages pile up unchecked until the per-wb freerun ceiling gets hit and IO is throttledb) while IO is throttled, the flusher is still not started, which means the writer basically sits in the throttle loop sleeping while waiting for dirty pages to be cleaned but no writeback is running
This leads to severe stalls and degraded throughput. On fuse, buffered write performance drops from 1400 MiB/s to 2000 KiB/s.
Quoted 6 lines
This fixes the issue by kicking off the flusher if
wb_dirtyexceedswb_bg_threshfor strictlimit BDIs. This restores performance back to its original baseline.Fixes 64dd89ae01f2 ("mm/block/fs: remove laptop_mode")Signed-off-by Joanne Koong <[email protected]>
Good spotting! I think your change makes sense but I don't think it is enough. The problem is that writeback throttling depends also on memcg setup so with your fix we still have a problem that when throttling due to memcg limits the flush work won't be queued early enough / at all. So I think the best fix is to perhaps do your change so that background writeback is started earlier for strictlimit bdis but also return back the unconditional starting of writeback (with properly updated comment) when we find out we're going to throttle the task for whatever reason.
Honza
Quoted 18 lines
mm/page-writeback.c +3
-1@@ -1835,7 +1835,9 @@ static int balance_dirty_pages(struct bdi_writeback *wb,balance_domain_limits (mdtc, strictlimit); } -if (nr_dirty > gdtc->bg_thresh && !writeback_in_progress (wb)) +if (!writeback_in_progress (wb) && + (nr_dirty > gdtc->bg_thresh || + (strictlimit && gdtc->wb_dirty > gdtc->wb_bg_thresh)))wb_start_background_writeback (wb);/* Signature · 1 line
2.52.0
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Quoted 36 lines · Jan Kara
Quoted 27 lines · Joanne Koong
Commit
64dd89ae01f2("mm/block/fs: removelaptop_mode") removed this unconditional writeback kick frombalance_dirty_pages():if (unlikely(!writeback_in_progress(wb))) wb_start_background_writeback(wb);Earlier in
balance_dirty_pages(), background writeback is started if the global dirty count exceeds the global background threshold (nr_dirty>gdtc->bg_thresh). However for BDIs withBDI_CAP_STRICTLIMITset (eg fuse), throttling is calculated using the per-wb threshold, not global thresholds. This means the per-wb threshold can be exceeded while the globalnr_dirtyis belowgdtc->bg_thresh. This causes two problems:a) background writeback is never proactively kicked off. The flusher should be kicked off while the writer is still free-running, so that dirty pages are drained before the writer hits the throttle threshold. For strictlimit BDIs with global
nr_dirty<gdtc->bg_thresh, this never kicks off the flusher, so dirty pages pile up unchecked until the per-wb freerun ceiling gets hit and IO is throttledb) while IO is throttled, the flusher is still not started, which means the writer basically sits in the throttle loop sleeping while waiting for dirty pages to be cleaned but no writeback is running
This leads to severe stalls and degraded throughput. On fuse, buffered write performance drops from 1400 MiB/s to 2000 KiB/s.
Quoted 6 lines
This fixes the issue by kicking off the flusher if
wb_dirtyexceedswb_bg_threshfor strictlimit BDIs. This restores performance back to its original baseline.Fixes 64dd89ae01f2 ("mm/block/fs: remove laptop_mode")Signed-off-by Joanne Koong <[email protected]>
Quoted 8 lines
Good spotting! I think your change makes sense but I don't think it is enough. The problem is that writeback throttling depends also on memcg setup so with your fix we still have a problem that when throttling due to memcg limits the flush work won't be queued early enough / at all. So I think the best fix is to perhaps do your change so that background writeback is started earlier for strictlimit bdis but also return back the unconditional starting of writeback (with properly updated comment) when we find out we're going to throttle the task for whatever reason.
Thanks for the explanation - great point about the memcg case.
I will bring back those 2 lines as the proper fix for the regression and submit this patch separately as a strictlimit optimization.
Thanks,
Joanne
Quoted 24 lines
Honza
Quoted 16 lines
mm/page-writeback.c +3
-2@@ -1835,7 +1835,9 @@ static int balance_dirty_pages(struct bdi_writeback *wb,balance_domain_limits (mdtc, strictlimit); } -if (nr_dirty > gdtc->bg_thresh && !writeback_in_progress (wb)) +if (!writeback_in_progress (wb) && + (nr_dirty > gdtc->bg_thresh || + (strictlimit && gdtc->wb_dirty > gdtc->wb_bg_thresh)))wb_start_background_writeback (wb);/* -- Quoted 2 lines
2.52.0
--
Jan Kara <[email protected]>
SUSE Labs, CR