From: Andrew Morton <akpm@linux-foundation.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: willy@infradead.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] writeback: factor out balance_wb_limits to remove repeated code
Date: Tue, 11 Jun 2024 14:52:56 -0700 [thread overview]
Message-ID: <20240611145256.41a857beb521df61cff1695a@linux-foundation.org> (raw)
In-Reply-To: <20240606033547.344376-1-shikemeng@huaweicloud.com>
On Thu, 6 Jun 2024 11:35:47 +0800 Kemeng Shi <shikemeng@huaweicloud.com> wrote:
> Factor out balance_wb_limits to remove repeated code
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> ---
> mm/page-writeback.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> index bf050abd9053..f611272d3c5b 100644
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -1783,6 +1783,21 @@ static inline void wb_dirty_exceeded(struct dirty_throttle_control *dtc,
> ((dtc->dirty > dtc->thresh) || strictlimit);
> }
>
> +/*
> + * The limits fileds dirty_exceeded and pos_ratio won't be updated if wb is
> + * in freerun state. Please don't use these invalid fileds in freerun case.
s/fileds/fields/. I queued a fix for this.
> + */
> +static void balance_wb_limits(struct dirty_throttle_control *dtc,
> + bool strictlimit)
> +{
> + wb_dirty_freerun(dtc, strictlimit);
> + if (dtc->freerun)
> + return;
> +
> + wb_dirty_exceeded(dtc, strictlimit);
> + wb_position_ratio(dtc);
> +}
> +
> /*
> * balance_dirty_pages() must be called by processes which are generating dirty
> * data. It looks at the number of dirty pages in the machine and will force
> @@ -1869,12 +1884,9 @@ static int balance_dirty_pages(struct bdi_writeback *wb,
> * Calculate global domain's pos_ratio and select the
> * global dtc by default.
> */
> - wb_dirty_freerun(gdtc, strictlimit);
> + balance_wb_limits(gdtc, strictlimit);
> if (gdtc->freerun)
> goto free_running;
Would it be neater to do
if (balance_wb_limits(...))
goto free_running;
?
That would require a balance_wb_limits() comment update and probably
name change. Just a thought.
next prev parent reply other threads:[~2024-06-11 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 3:35 Kemeng Shi
2024-06-11 21:52 ` Andrew Morton [this message]
2024-06-13 8:51 ` Kemeng Shi
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=20240611145256.41a857beb521df61cff1695a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shikemeng@huaweicloud.com \
--cc=willy@infradead.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