From: chi wu <wuchi.zero@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, tj@kernel.org,
Howard Cochran <hcochran@kernelspring.com>,
Miklos Szeredi <mszeredi@redhat.com>, Jens Axboe <axboe@fb.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] mm/page-writeback: Fix performance when BDI's share of ratio is 0.
Date: Mon, 10 May 2021 18:22:53 +0800 [thread overview]
Message-ID: <CA+tQmHBvm41BbYJXVqAR+RDy1R9WJXP7TmkqkgpigOUh45QpXg@mail.gmail.com> (raw)
In-Reply-To: <20210509163633.ced3588cb92984c0d3835fc3@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> 于2021年5月10日周一 上午7:36写道:
>
> On Thu, 29 Apr 2021 06:50:46 +0800 Chi Wu <wuchi.zero@gmail.com> wrote:
>
> > Fix performance when BDI's share of ratio is 0.
> >
> > The issue is similar to commit 74d369443325 ("writeback: Fix
> > performance regression in wb_over_bg_thresh()").
> >
> > Balance_dirty_pages and the writeback worker will also disagree on
> > whether writeback when a BDI uses BDI_CAP_STRICTLIMIT and BDI's share
> > of the thresh ratio is zero.
> >
> > For example, A thread on cpu0 writes 32 pages and then
> > balance_dirty_pages, it will wake up background writeback and pauses
> > because wb_dirty > wb->wb_thresh = 0 (share of thresh ratio is zero).
> > A thread may runs on cpu0 again because scheduler prefers pre_cpu.
> > Then writeback worker may runs on other cpus(1,2..) which causes the
> > value of wb_stat(wb, WB_RECLAIMABLE) in wb_over_bg_thresh is 0 and does
> > not writeback and returns.
> >
> > Thus, balance_dirty_pages keeps looping, sleeping and then waking up the
> > worker who will do nothing. It remains stuck in this state until the
> > writeback worker hit the right dirty cpu or the dirty pages expire.
> >
> > The fix that we should get the wb_stat_sum radically when thresh is low.
>
> (optimistically Cc's various people who might remember how this code works)
Thanks, I'll correct it in the future.
>
> > Signed-off-by: Chi Wu <wuchi.zero@gmail.com>
>
> Thanks. I'll add it for some testing and hopefully someone will find
> the time to review this.
>
> > ---
> > mm/page-writeback.c | 20 ++++++++++++++++----
> > 1 file changed, 16 insertions(+), 4 deletions(-)
> >
> > diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> > index 0062d5c57d41..bd7052295246 100644
> > --- a/mm/page-writeback.c
> > +++ b/mm/page-writeback.c
> > @@ -1945,6 +1945,8 @@ bool wb_over_bg_thresh(struct bdi_writeback *wb)
> > struct dirty_throttle_control * const gdtc = &gdtc_stor;
> > struct dirty_throttle_control * const mdtc = mdtc_valid(&mdtc_stor) ?
> > &mdtc_stor : NULL;
> > + unsigned long reclaimable;
> > + unsigned long thresh;
> >
> > /*
> > * Similar to balance_dirty_pages() but ignores pages being written
> > @@ -1957,8 +1959,13 @@ bool wb_over_bg_thresh(struct bdi_writeback *wb)
> > if (gdtc->dirty > gdtc->bg_thresh)
> > return true;
> >
> > - if (wb_stat(wb, WB_RECLAIMABLE) >
> > - wb_calc_thresh(gdtc->wb, gdtc->bg_thresh))
> > + thresh = wb_calc_thresh(gdtc->wb, gdtc->bg_thresh);
> > + if (thresh < 2 * wb_stat_error())
> > + reclaimable = wb_stat_sum(wb, WB_RECLAIMABLE);
> > + else
> > + reclaimable = wb_stat(wb, WB_RECLAIMABLE);
> > +
> > + if (reclaimable > thresh)
> > return true;
> >
> > if (mdtc) {
> > @@ -1972,8 +1979,13 @@ bool wb_over_bg_thresh(struct bdi_writeback *wb)
> > if (mdtc->dirty > mdtc->bg_thresh)
> > return true;
> >
> > - if (wb_stat(wb, WB_RECLAIMABLE) >
> > - wb_calc_thresh(mdtc->wb, mdtc->bg_thresh))
> > + thresh = wb_calc_thresh(mdtc->wb, mdtc->bg_thresh);
> > + if (thresh < 2 * wb_stat_error())
> > + reclaimable = wb_stat_sum(wb, WB_RECLAIMABLE);
> > + else
> > + reclaimable = wb_stat(wb, WB_RECLAIMABLE);
> > +
> > + if (reclaimable > thresh)
> > return true;
> > }
> >
> > --
> > 2.17.1
next prev parent reply other threads:[~2021-05-10 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 22:50 Chi Wu
2021-05-08 2:17 ` chi wu
2021-05-08 2:31 ` chi wu
2021-05-09 23:36 ` Andrew Morton
2021-05-10 10:22 ` chi wu [this message]
2021-05-10 10:44 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+tQmHBvm41BbYJXVqAR+RDy1R9WJXP7TmkqkgpigOUh45QpXg@mail.gmail.com \
--to=wuchi.zero@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=hcochran@kernelspring.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mszeredi@redhat.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox