From: Hiroshi Nishida <nishidafmly@gmail.com>
To: 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,
Hiroshi Nishida <nishidafmly@gmail.com>
Subject: [PATCH 0/2] md/raid5: reduce resync/recovery dispatch overhead
Date: Fri, 10 Jul 2026 06:23:37 -0700 [thread overview]
Message-ID: <20260710132339.7284-1-nishidafmly@gmail.com> (raw)
Two changes to how resync/recovery submits work, reducing per-stripe
overhead on the rebuild path. Neither adds memory.
1/2 submits a window of stripes per raid5_sync_request() call instead
of one at a time. On a rebuild this reduces the number of
raid5_sync_request() invocations by ~30x (a call-count measurement,
not a throughput figure) and bounds the per-stripe jiffy-sleep that
otherwise throttles progress when the stripe cache is under
pressure.
2/2 reserves a small amount of stripe cache for user I/O during a
rebuild, so foreground I/O is not starved by the resync stream. A
pure rebuild with no competing I/O is unchanged.
Both touch only the resync/recovery path and are independent of the other
md patches I'm sending separately.
Hiroshi Nishida (2):
md/raid5: submit a window of stripes during resync/recovery
md/raid5: reserve stripe cache for user I/O during rebuild
drivers/md/raid5.c | 68 +++++++++++++++++++++++++++++++++++++---------
drivers/md/raid5.h | 2 ++
2 files changed, 57 insertions(+), 13 deletions(-)
base-commit: 55b77337bdd088c77461588e5ec094421b89911b
--
2.43.0
next reply other threads:[~2026-07-10 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 13:23 Hiroshi Nishida [this message]
2026-07-10 13:23 ` [PATCH 1/2] md/raid5: submit a window of stripes during resync/recovery Hiroshi Nishida
2026-07-10 13:36 ` sashiko-bot
2026-07-10 13:23 ` [PATCH 2/2] md/raid5: reserve stripe cache for user I/O during rebuild Hiroshi Nishida
2026-07-10 13:34 ` sashiko-bot
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=20260710132339.7284-1-nishidafmly@gmail.com \
--to=nishidafmly@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
--cc=yukuai@fygo.io \
/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