From: Pavel Machek <pavel@denx.de>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, cip-dev@lists.cip-project.org
Subject: Re: [PATCH 6.12.y-cip] mm: page_alloc: Add kernel parameter to select maximum PCP batch scale number
Date: Wed, 29 Oct 2025 10:24:06 +0100 [thread overview]
Message-ID: <aQHdNhBR2DiWAtEx@duo.ucw.cz> (raw)
In-Reply-To: <20251027092658.84955-1-claudiu.beznea.uj@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
Hi!
> Commit 52166607ecc9 ("mm: restrict the pcp batch scale factor to avoid
> too long latency") introduced default PCP (Per-CPU Pageset) batch size as
> a configuration flag. The configuration flag is CONFIG_PCP_BATCH_SCALE_MAX.
>
> The ARM64 defconfig has CONFIG_PCP_BATCH_SCALE_MAX=5. This defconfig
> is used by a high range of SoCs.
>
> The Renesas RZ/G3S SoC is a single CPU SoC, with L1$ (I-cache 32Kbytes,
> D-cache 32 Kbytes), L3$ (256 Kbytes), but no L2$. It is currently used in
> a configuration with 1 GiB RAM size. In this configuration, starting with
> commit 52166607ecc9 ("mm: restrict the pcp batch scale factor to avoid too
> long latency") the "bonnie++ -d /mnt -u root" benchmark takes ~14 minutes
> while previously it took ~10 minutes. The /mnt directory is mounted on SD
> card. Same behavior is reproduced on similar Renesas single core devices
> (e.g., Renesas RZ/G2UL). bonnie++ version used was 1.04.
>
> Add a new kernel parameter to allow systems like Renesas RZ/G3S to
> continue have the same performance numbers with the default mainline
...
> This patch was posted as RFC at [1] but got no feedback. Starting with
> kernel v6.17 the behaviour was restored by commits:
>
> 18ebe55a9236 ("mm/readahead: terminate async readahead on natural boundary")
> 38b0ece6d763 ("mm/filemap: allow arch to request folio size for exec
> memory")
Ok, so this is not mainline, because mainline has different solution.
It is also not queued for stable.
It introduces kernel parameter that will be special for -cip, not seen
in mainline nor -stable.
Presumably you'll be telling your customers to set the command line
parameter. Would it make sense to ask them to tune the config instead?
Best regards,
Pavel
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4734,6 +4734,12 @@
> for debug and development, but should not be
> needed on a platform with proper driver support.
>
> + pcp_batch_scale_max=n
> + Format: <integer>
> + Range: 0,6 : number
> + Default : CONFIG_PCP_BATCH_SCALE_MAX
> + Used for setting the scale number for PCP batch scale algorithm.
> +
> pdcchassis= [PARISC,HW] Disable/Enable PDC Chassis Status codes at
> boot time.
> Format: { 0 | 1 }
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-10-29 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 9:26 [PATCH 6.12.y-cip] mm: page_alloc: Add kernel parameter to select maximum PCP batch scale number Claudiu
2025-10-29 9:24 ` Pavel Machek [this message]
2025-10-29 14:30 ` claudiu beznea
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=aQHdNhBR2DiWAtEx@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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