linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: 76824143@qq.com
Cc: linux-mm@kvack.org, Hao Zhang <zhanghao1@kylinos.cn>
Subject: Re: [PATCH] mm/vmscan: extract calculated pressure balance as a function
Date: Fri, 10 Jan 2025 17:42:29 -0800	[thread overview]
Message-ID: <20250110174229.34cba2485e41d988ec37b4f5@linux-foundation.org> (raw)
In-Reply-To: <tencent_67C81E7076A100A129F35AA610DBC14CCD05@qq.com>

On Fri, 10 Jan 2025 11:17:47 +0800 76824143@qq.com wrote:

> From: Hao Zhang <zhanghao1@kylinos.cn>
> 
> The pressure balance calculation is only used in the
> fraction scenario. Extract into functions to avoid
> unnecessary calculations. This doesn't change current
> behaviour.

The code which has been moved was only executed after setting
`scan_balance = SCAN_FRACT', so there are presently no "unnecessary
calculations", unless I'm missing something.

And the new `bool calculated' had to be added to avoid creating
"unnecessary calculations".

So I'm not seeing any benefit here.

I guess as a little cleanup we could move all that code into the new
calculate_pressure_balance() and call calculate_pressure_balance() in
the same place (just after `scan_balance = SCAN_FRACT;').  The compiler
should inline calculate_pressure_balance() so no runtime effect.

> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2367,6 +2367,43 @@ static void prepare_scan_control(pg_data_t *pgdat, struct scan_control *sc)
>  	}
>  }
>  
> +static void calculate_pressure_balance(struct scan_control *sc, int swappiness,
> +			u64 *fraction, u64 *denominator)
> +{
> +	unsigned long anon_cost, file_cost, total_cost;
> +	unsigned long ap, fp;
> +
> +	/*
> +	 * Calculate the pressure balance between anon and file pages.
> +	 *
> +	 * The amount of pressure we put on each LRU is inversely
> +	 * proportional to the cost of reclaiming each list, as
> +	 * determined by the share of pages that are refaulting, times
> +	 * the relative IO cost of bringing back a swapped out
> +	 * anonymous page vs reloading a filesystem page (swappiness).
> +	 *
> +	 * Although we limit that influence to ensure no list gets
> +	 * left behind completely: at least a third of the pressure is
> +	 * applied, before swappiness.
> +	 *
> +	 * With swappiness at 100, anon and file have equal IO cost.
> +	 */

And this comment could perhaps be moved into the introductory comment
above the calculate_pressure_balance() site.

I don't know if the end result would represent much improvement though.

> +	total_cost = sc->anon_cost + sc->file_cost;
> +	anon_cost = total_cost + sc->anon_cost;
> +	file_cost = total_cost + sc->file_cost;
> +	total_cost = anon_cost + file_cost;
> +
> +	ap = swappiness * (total_cost + 1);
> +	ap /= anon_cost + 1;
> +
> +	fp = (MAX_SWAPPINESS - swappiness) * (total_cost + 1);
> +	fp /= file_cost + 1;
> +
> +	fraction[WORKINGSET_ANON] = ap;
> +	fraction[WORKINGSET_FILE] = fp;
> +	*denominator = ap + fp;
> +}
> +



      reply	other threads:[~2025-01-11  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  3:17 76824143
2025-01-11  1:42 ` Andrew Morton [this message]

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=20250110174229.34cba2485e41d988ec37b4f5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=76824143@qq.com \
    --cc=linux-mm@kvack.org \
    --cc=zhanghao1@kylinos.cn \
    /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