From: "Yu Kuai" <yukuai@fnnas.com>
To: "Abd-Alrhman Masalkhi" <abd.masalkhi@gmail.com>, <song@kernel.org>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yukuai@fnnas.com>
Subject: Re: [PATCH] md: skip redundant raid_disks update when value is unchanged
Date: Tue, 28 Apr 2026 16:25:09 +0800 [thread overview]
Message-ID: <9748ccf8-7d4f-495f-8083-eb640008f073@fnnas.com> (raw)
In-Reply-To: <20260425085843.3725-1-abd.masalkhi@gmail.com>
Hi,
在 2026/4/25 16:58, Abd-Alrhman Masalkhi 写道:
> Calling update_raid_disks() with the same value as the current one
> can trigger unnecessary work. For example, RAID1 will reallocate
> resources such as the mempool for r1bio.
>
> Signed-off-by: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
> ---
> It returns -EINVAL for the same value. If silent success is preferred
> instead, please let me know so I adjust its behavior.
> ---
> drivers/md/md.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 0e55639211f2..cb66c4ebbafa 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -4409,9 +4409,12 @@ raid_disks_store(struct mddev *mddev, const char *buf, size_t len)
> err = mddev_suspend_and_lock(mddev);
> if (err)
> return err;
> - if (mddev->pers)
> - err = update_raid_disks(mddev, n);
> - else if (mddev->reshape_position != MaxSector) {
> + if (mddev->pers) {
> + if (n != mddev->raid_disks)
> + err = update_raid_disks(mddev, n);
> + else
> + err = -EINVAL;
Changing return value in this case is not expected, especially from
success to failure.
> + } else if (mddev->reshape_position != MaxSector) {
> struct md_rdev *rdev;
> int olddisks = mddev->raid_disks - mddev->delta_disks;
>
--
Thansk,
Kuai
next prev parent reply other threads:[~2026-04-28 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 8:58 [PATCH] md: skip redundant raid_disks update when value is unchanged Abd-Alrhman Masalkhi
2026-04-28 8:25 ` Yu Kuai [this message]
2026-04-28 9:56 ` Abd-Alrhman Masalkhi
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=9748ccf8-7d4f-495f-8083-eb640008f073@fnnas.com \
--to=yukuai@fnnas.com \
--cc=abd.masalkhi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@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