From: Zdenek Kabelac <zkabelac@redhat.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Nikolay Borisov <nborisov@suse.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6?
Date: Thu, 16 Nov 2017 10:43:37 +0100 [thread overview]
Message-ID: <6e0f8a37-c3f8-61f0-d51d-01b72c3c65b7@redhat.com> (raw)
In-Reply-To: <354402cd-587d-72d8-aaa1-87a1b5c9f03c@gmx.com>
Dne 16.11.2017 v 09:08 Qu Wenruo napsal(a):
>
>
>>>>>>
>>>>> [What we have]
>>>>> The nearest infrastructure I found in kernel is bio_integrity_payload.
>>>>>
Hi
We already have dm-integrity target upstream.
What's missing in this target ?
Regards
Zdenek
next prev parent reply other threads:[~2017-11-16 9:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 2:18 Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6? Qu Wenruo
2017-11-16 6:54 ` Nikolay Borisov
2017-11-16 7:38 ` Qu Wenruo
2017-11-16 7:42 ` Nikolay Borisov
2017-11-16 8:08 ` Qu Wenruo
2017-11-16 9:43 ` Zdenek Kabelac [this message]
2017-11-16 10:04 ` Qu Wenruo
2017-11-16 12:33 ` Zdenek Kabelac
2017-11-16 12:41 ` Austin S. Hemmelgarn
2017-11-16 14:06 ` Qu Wenruo
2017-11-16 16:47 ` Austin S. Hemmelgarn
2017-11-16 21:05 ` Pasi Kärkkäinen
2017-11-17 1:30 ` Qu Wenruo
2017-11-17 12:22 ` Austin S. Hemmelgarn
2017-11-16 22:32 ` Chris Murphy
2017-11-17 1:22 ` Qu Wenruo
2017-11-17 1:54 ` Chris Murphy
2017-11-17 1:55 ` Chris Murphy
2017-11-21 2:53 ` [dm-devel] " Theodore Ts'o
2017-11-17 1:26 ` Andreas Dilger
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=6e0f8a37-c3f8-61f0-d51d-01b72c3c65b7@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nborisov@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).