[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d41f0296-45b9-4264-adc8-f41601b36edd@suse.de>
Date: Tue, 27 May 2025 08:17:47 +0200
From: Hannes Reinecke <hare@...e.de>
To: Yu Kuai <yukuai1@...weicloud.com>, hch@....de, xni@...hat.com,
colyli@...nel.org, song@...nel.org, yukuai3@...wei.com
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
johnny.chenyi@...wei.com
Subject: Re: [PATCH 10/23] md: add a new recovery_flag
MD_RECOVERY_LAZY_RECOVER
On 5/24/25 08:13, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@...wei.com>
>
> This flag is used by llbitmap in later patches to skip raid456 initial
> recover and delay building initial xor data to first write.
>
> Signed-off-by: Yu Kuai <yukuai3@...wei.com>
> Reviewed-by: Christoph Hellwig <hch@....de>
> ---
> drivers/md/md.c | 12 +++++++++++-
> drivers/md/md.h | 2 ++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
Wouldn't it be enough to check for the 'blocks_synced' callback to check
if the array supports lazy recovery?
Otherwise:
Reviewed-by: Hannes Reinecke <hare@...e.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
Powered by blists - more mailing lists