All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-raid@vger.kernel.org,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: About the md-bitmap behavior
Date: Mon, 20 Jun 2022 10:56:06 +0100	[thread overview]
Message-ID: <06365833-bd91-7dcf-4541-f8e15ed3bef2@youngman.org.uk> (raw)
In-Reply-To: <1704788b-fb7d-b532-4911-238e4f7fd448@gmx.com>

On 20/06/2022 08:56, Qu Wenruo wrote:
>> The write-hole has been addressed with journaling already, and this will
>> be adding a new and not-needed feature - not saying it wouldn't be nice
>> to have, but do we need another way to skin this cat?
> 
> I'm talking about the BTRFS RAID56, not md-raid RAID56, which is a
> completely different thing.
> 
> Here I'm just trying to understand how the md-bitmap works, so that I
> can do a proper bitmap for btrfs RAID56.

Ah. Okay.

Neil Brown is likely to be the best help here as I believe he wrote a 
lot of the code, although I don't think he's much involved with md-raid 
any more.

Cheers,
Wol

  reply	other threads:[~2022-06-20  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  7:29 About the md-bitmap behavior Qu Wenruo
2022-06-20  7:48 ` Wols Lists
2022-06-20  7:56   ` Qu Wenruo
2022-06-20  9:56     ` Wols Lists [this message]
2022-06-22  2:15       ` Doug Ledford
2022-06-22  2:37         ` Qu Wenruo
2022-06-22 22:32           ` NeilBrown
2022-06-22 23:00             ` Song Liu
2022-06-23  0:53               ` Qu Wenruo
2022-06-23  0:39             ` Qu Wenruo
2022-06-23  3:32               ` Song Liu
2022-06-23  4:52                 ` Qu Wenruo
2022-06-24  0:55                   ` Jani Partanen
2022-06-24  1:35                     ` Qu Wenruo

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=06365833-bd91-7dcf-4541-f8e15ed3bef2@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.