From: "yu kuai" <yukuai@fygo.io>
To: "Hiroshi Nishida" <nishidafmly@gmail.com>,
"Song Liu" <song@kernel.org>, "yu kuai" <yukuai@fygo.io>
Cc: "Li Nan" <magiclinan@didiglobal.com>, "Xiao Ni" <xiao@kernel.org>,
<linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] md/raid5: scale the default stripe cache size with system memory
Date: Fri, 31 Jul 2026 05:17:25 +0800 [thread overview]
Message-ID: <158faaad-0542-4187-8158-eab5b9876d29@fygo.io> (raw)
In-Reply-To: <20260710132346.7295-6-nishidafmly@gmail.com>
Hi,
在 2026/7/10 21:23, Hiroshi Nishida 写道:
> setup_conf() starts every array with min_nr_stripes = NR_STRIPES (256),
> about 12MB of stripe cache on a 12-disk array. That fixed default was
> chosen for small systems and is never revisited: a server with hundreds
> of GB of RAM backing a wide array still creates its arrays with the same
> 256 stripes, and only benefits from more after an administrator writes
> stripe_cache_size by hand.
>
> Auto-size the initial count from memory when the new
> stripe_cache_size_default module parameter is 0 (the default): keep the
> historical NR_STRIPES up to RAID5_CACHE_DEFAULT_BASE_GB (8GB) of RAM, then
> grow the count using about 1/512 of the RAM above that baseline, capped at
> RAID5_CACHE_DEFAULT_MAX (4096). A system with 8GB or less is therefore
> unchanged -- same count, same footprint -- while larger ones scale up
> smoothly (no jump at the baseline) to a bounded maximum. A non-zero
> stripe_cache_size_default sets a fixed initial size for administrators who
> want one; existing arrays are unaffected, and a reshape still forces at
> least its window's worth of stripes.
I will not accept changing the default value for now, unless it's tested and
validated across various architectures and environments.
BTW, if you want to do this, I'll suggest you write a user space tool.
>
> Signed-off-by: Hiroshi Nishida <nishidafmly@gmail.com>
> ---
> drivers/md/raid5.c | 44 +++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 41 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 5f0825c5effe..8e1c2eba4241 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -83,6 +83,11 @@ module_param(max_stripe_batch, uint, 0644);
> MODULE_PARM_DESC(max_stripe_batch,
> "Number of stripes a worker thread handles per device_lock acquisition, 1-32 (default 8). Larger values amortise the lock over more stripes on busy multi-threaded arrays at some latency cost. Read when an array is created");
>
> +static unsigned int stripe_cache_size_default;
> +module_param(stripe_cache_size_default, uint, 0644);
> +MODULE_PARM_DESC(stripe_cache_size_default,
> + "Initial stripe_cache_size for newly created arrays. 0 (the default) auto-sizes it from system memory: the historical 256 on small hosts, scaling up with RAM to a capped maximum on larger ones. A non-zero value sets a fixed initial size. Existing arrays are unaffected");
> +
> static bool devices_handle_discard_safely = false;
> module_param(devices_handle_discard_safely, bool, 0644);
> MODULE_PARM_DESC(devices_handle_discard_safely,
> @@ -7568,6 +7573,17 @@ static unsigned long raid5_cache_count(struct shrinker *shrink,
> return max_stripes - min_stripes;
> }
>
> +/*
> + * Auto-sizing of the initial stripe cache (stripe_cache_size_default == 0):
> + * stay at the historical NR_STRIPES up to RAID5_CACHE_DEFAULT_BASE_GB of RAM,
> + * then grow the count using about 1/512 of the RAM above that base, capped at
> + * RAID5_CACHE_DEFAULT_MAX. So a system at or below the base is unchanged and
> + * keeps the historical footprint, while larger ones scale.
> + */
> +#define RAID5_CACHE_DEFAULT_BASE_GB 8 /* unchanged at or below this much RAM */
> +#define RAID5_CACHE_DEFAULT_RAM_SHIFT 9 /* above it: ~1/512 of the extra RAM */
> +#define RAID5_CACHE_DEFAULT_MAX 4096
> +
> static struct r5conf *setup_conf(struct mddev *mddev)
> {
> struct r5conf *conf;
> @@ -7801,15 +7817,37 @@ static struct r5conf *setup_conf(struct mddev *mddev)
> conf->prev_algo = conf->algorithm;
> }
>
> - conf->min_nr_stripes = NR_STRIPES;
> + /*
> + * Choose the initial stripe cache size. stripe_cache_size_default
> + * selects it: 0 (the default) auto-sizes from memory -- the historical
> + * NR_STRIPES up to RAID5_CACHE_DEFAULT_BASE_GB of RAM, then scaling up
> + * to at most RAID5_CACHE_DEFAULT_MAX -- and a non-zero value sets it
> + * directly. A reshape still forces at least enough stripes for its
> + * window, below.
> + */
> + if (stripe_cache_size_default) {
> + conf->min_nr_stripes = clamp_t(unsigned long,
> + stripe_cache_size_default, 16, INT_MAX);
> + } else {
> + unsigned long per_stripe = sizeof(struct stripe_head) +
> + max_disks * (sizeof(struct bio) + PAGE_SIZE);
> + unsigned long ram = totalram_pages() << PAGE_SHIFT;
> + unsigned long base = (unsigned long)RAID5_CACHE_DEFAULT_BASE_GB << 30;
> + unsigned long extra = ram > base ?
> + ((ram - base) >> RAID5_CACHE_DEFAULT_RAM_SHIFT) / per_stripe : 0;
> +
> + conf->min_nr_stripes = clamp_t(unsigned long, NR_STRIPES + extra,
> + NR_STRIPES, RAID5_CACHE_DEFAULT_MAX);
> + }
> if (mddev->reshape_position != MaxSector) {
> int stripes = max_t(int,
> ((mddev->chunk_sectors << 9) / RAID5_STRIPE_SIZE(conf)) * 4,
> ((mddev->new_chunk_sectors << 9) / RAID5_STRIPE_SIZE(conf)) * 4);
> - conf->min_nr_stripes = max(NR_STRIPES, stripes);
> - if (conf->min_nr_stripes != NR_STRIPES)
> + if (stripes > conf->min_nr_stripes) {
> + conf->min_nr_stripes = stripes;
> pr_info("md/raid:%s: force stripe size %d for reshape\n",
> mdname(mddev), conf->min_nr_stripes);
> + }
> }
> memory = conf->min_nr_stripes * (sizeof(struct stripe_head) +
> max_disks * ((sizeof(struct bio) + PAGE_SIZE))) / 1024;
--
Thanks,
Kuai
next prev parent reply other threads:[~2026-07-30 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 13:23 [PATCH 0/6] md/raid5: size stripe-cache and worker tuning from the hardware Hiroshi Nishida
2026-07-10 13:23 ` [PATCH 1/6] md/raid5: size the worker group array by nr_node_ids Hiroshi Nishida
2026-07-30 20:25 ` yu kuai
2026-07-10 13:23 ` [PATCH 2/6] md/raid5: size stripe-cache hash locks from the CPU count Hiroshi Nishida
2026-07-30 20:26 ` yu kuai
2026-07-10 13:23 ` [PATCH 3/6] md/raid5: scale the stripe_cache_size limit with system memory Hiroshi Nishida
2026-07-30 21:01 ` yu kuai
2026-07-10 13:23 ` [PATCH 4/6] md/raid5: make the stripe batch size a module parameter Hiroshi Nishida
2026-07-30 21:12 ` yu kuai
2026-07-10 13:23 ` [PATCH 5/6] md/raid5: scale the default stripe cache size with system memory Hiroshi Nishida
2026-07-30 21:17 ` yu kuai [this message]
2026-07-10 13:23 ` [PATCH 6/6] md/raid5: derive the default group_thread_cnt from the hardware Hiroshi Nishida
2026-07-30 21:20 ` yu kuai
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=158faaad-0542-4187-8158-eab5b9876d29@fygo.io \
--to=yukuai@fygo.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=nishidafmly@gmail.com \
--cc=song@kernel.org \
--cc=xiao@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
all inboxes | Powered by JetHome®