public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yu Kuai" <yukuai@fnnas.com>
To: <linux-raid@vger.kernel.org>, <song@kernel.org>
Cc: <linan122@huawei.com>, <xni@redhat.com>, <yukuai@fnnas.com>
Subject: Re: [PATCH v3 0/3] md/md-llbitmap: add CleanUnwritten support
Date: Tue, 7 Apr 2026 13:29:43 +0800	[thread overview]
Message-ID: <dd81d0d8-b027-43dd-b2bb-4d29ba96706b@fnnas.com> (raw)
In-Reply-To: <20260323054644.3351791-1-yukuai@fnnas.com>

在 2026/3/23 13:46, Yu Kuai 写道:

> Patch 1 improves compatibility with older mdadm versions by detecting
> on-disk bitmap version and falling back to the correct bitmap_ops when
> there's a version mismatch.
>
> Patch 2 adds support for proactive XOR parity building in RAID-456 arrays.
> This allows users to pre-build parity for unwritten regions via sysfs
> before any user data is written, which can improve write performance for
> workloads that will eventually use all storage. New states (CleanUnwritten,
> NeedSyncUnwritten, SyncingUnwritten) are added to track these regions
> separately from normal dirty/syncing states.
>
> Patch 3 optimizes initial array sync for RAID-456 arrays on devices that
> support write_zeroes with unmap. By zeroing all disks upfront, parity is
> automatically consistent (0 XOR 0 = 0), allowing the bitmap to be
> initialized to BitCleanUnwritten and skipping the initial sync entirely.
> This significantly reduces array initialization time on modern NVMe SSDs.
>
> Yu Kuai (3):
>    md: add fallback to correct bitmap_ops on version mismatch
>    md/md-llbitmap: add CleanUnwritten state for RAID-5 proactive parity
>      building
>    md/md-llbitmap: optimize initial sync with write_zeroes_unmap support
>
>   drivers/md/md-llbitmap.c | 202 ++++++++++++++++++++++++++++++++++++---
>   drivers/md/md.c          | 111 ++++++++++++++++++++-
>   2 files changed, 299 insertions(+), 14 deletions(-)
Applied to md-7.1

-- 
Thansk,
Kuai

      parent reply	other threads:[~2026-04-07  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  5:46 [PATCH v3 0/3] md/md-llbitmap: add CleanUnwritten support Yu Kuai
2026-03-23  5:46 ` [PATCH v3 1/3] md: add fallback to correct bitmap_ops on version mismatch Yu Kuai
2026-03-23  5:46 ` [PATCH v3 2/3] md/md-llbitmap: add CleanUnwritten state for RAID-5 proactive parity building Yu Kuai
2026-03-23  5:46 ` [PATCH v3 3/3] md/md-llbitmap: optimize initial sync with write_zeroes_unmap support Yu Kuai
2026-04-07  5:29 ` Yu Kuai [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=dd81d0d8-b027-43dd-b2bb-4d29ba96706b@fnnas.com \
    --to=yukuai@fnnas.com \
    --cc=linan122@huawei.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    /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