mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yu Kuai" <yukuai@fnnas.com>
To: <song@kernel.org>
Cc: <linan122@huawei.com>, <xni@redhat.com>, <colyli@fnnas.com>,
	 <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <yukuai@fnnas.com>
Subject: Re: [PATCH v2 0/5] md/md-llbitmap: fixes and proactive parity building support
Date: Mon, 23 Mar 2026 02:30:25 +0800	[thread overview]
Message-ID: <1bb3659d-4911-4cd8-bb2c-d2399e5a02c2@fnnas.com> (raw)
In-Reply-To: <20260223024038.3084853-1-yukuai@fnnas.com>

在 2026/2/23 10:40, Yu Kuai 写道:
> Changes in v2:
>   - add error message in error path in patch 3;
>
> This series contains fixes and enhancements for the md-llbitmap (lockless
> bitmap) implementation.
>
> Patches 1-2 are bug fixes:
> - Patch 1 fixes bitmap data being read from spare disks that are not yet
>    in sync, which could lead to incorrect dirty bit tracking.
> - Patch 2 fixes a race condition where the state machine could transition
>    before the barrier is properly raised.
>
> Patch 3 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 4 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 5 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 (5):
>    md/md-llbitmap: skip reading rdevs that are not in_sync
>    md/md-llbitmap: raise barrier before state machine transition
>    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 | 213 +++++++++++++++++++++++++++++++++++----
>   drivers/md/md.c          | 117 ++++++++++++++++++++-
>   2 files changed, 309 insertions(+), 21 deletions(-)

Apply patch 1 and 2 to md-7.1, will send a new version for others soon.

-- 
Thansk,
Kuai

      parent reply	other threads:[~2026-03-22 18:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  2:40 Yu Kuai
2026-02-23  2:40 ` [PATCH v2 1/5] md/md-llbitmap: skip reading rdevs that are not in_sync Yu Kuai
2026-03-09  7:32   ` Xiao Ni
2026-02-23  2:40 ` [PATCH v2 2/5] md/md-llbitmap: raise barrier before state machine transition Yu Kuai
2026-03-09 13:05   ` Xiao Ni
2026-03-15 16:57     ` Yu Kuai
2026-02-23  2:40 ` [PATCH v2 3/5] md: add fallback to correct bitmap_ops on version mismatch Yu Kuai
2026-03-10  1:06   ` Xiao Ni
2026-03-15 17:01     ` Yu Kuai
2026-02-23  2:40 ` [PATCH v2 4/5] md/md-llbitmap: add CleanUnwritten state for RAID-5 proactive parity building Yu Kuai
2026-03-13  3:16   ` Xiao Ni
2026-03-17  3:36     ` Yu Kuai
2026-02-23  2:40 ` [PATCH v2 5/5] md/md-llbitmap: optimize initial sync with write_zeroes_unmap support Yu Kuai
2026-03-13  8:12   ` Xiao Ni
2026-03-22 18:30 ` 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=1bb3659d-4911-4cd8-bb2c-d2399e5a02c2@fnnas.com \
    --to=yukuai@fnnas.com \
    --cc=colyli@fnnas.com \
    --cc=linan122@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®