From: Chris Murphy <lists@colorremedies.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Brendan Hide <brendan@swiftspirit.co.za>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RedHat 7.4 Release Notes: "Btrfs has been deprecated" - wut?
Date: Mon, 7 Aug 2017 09:27:09 -0600 [thread overview]
Message-ID: <CAJCQCtRGUBWD6Mw6pAiKGAPgGz+vqy3sgmbEBDETPYsxJw8G7w@mail.gmail.com> (raw)
In-Reply-To: <4c094049-f8c8-a0ea-674b-33c6905d744a@gmx.com>
On Fri, Aug 4, 2017 at 8:05 AM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>
> For example, if one day there is some dm-csum to support verify csum of
> given ranges (and skip unrelated ones specified by higher levels), btrfs
> support for data csum is no longer an exclusive feature.
How would dm-csum differ from dm-integrity?
https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.txt
By that description it uses a journal to guarantee atomicity. If
multiqueue maybe the performance implications are neutral. But
certainly on spinning drives that would slow things down, especially
if the file system is also journaling, and the workload is metadata
heavy.
--
Chris Murphy
next prev parent reply other threads:[~2017-08-07 15:27 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 8:38 RedHat 7.4 Release Notes: "Btrfs has been deprecated" - wut? Brendan Hide
2017-08-02 9:11 ` Wang Shilong
2017-08-03 19:18 ` Chris Murphy
2017-08-02 11:25 ` Austin S. Hemmelgarn
2017-08-02 12:55 ` Lutz Vieweg
2017-08-02 13:47 ` Austin S. Hemmelgarn
2017-08-02 18:44 ` Chris Mason
2017-08-02 22:12 ` Fajar A. Nugraha
2017-08-02 22:22 ` Chris Murphy
2017-08-03 9:59 ` Lutz Vieweg
2017-08-03 18:08 ` waxhead
2017-08-03 18:29 ` Christoph Anton Mitterer
2017-08-03 19:22 ` Austin S. Hemmelgarn
2017-08-03 20:45 ` Brendan Hide
2017-08-03 22:00 ` Chris Murphy
2017-08-04 11:26 ` Austin S. Hemmelgarn
2017-08-03 19:03 ` Austin S. Hemmelgarn
2017-08-04 9:48 ` Duncan
2017-08-16 18:07 ` David Sterba
2017-08-04 14:05 ` Qu Wenruo
2017-08-04 23:55 ` Wang Shilong
2017-08-07 15:27 ` Chris Murphy [this message]
2017-08-10 0:35 ` Qu Wenruo
2017-08-12 0:10 ` Christoph Anton Mitterer
2017-08-12 7:42 ` Christoph Hellwig
2017-08-12 11:51 ` Christoph Anton Mitterer
2017-08-12 12:12 ` Hugo Mills
2017-08-13 14:08 ` Goffredo Baroncelli
2017-08-14 7:08 ` Qu Wenruo
2017-08-14 14:23 ` Goffredo Baroncelli
2017-08-14 19:08 ` Chris Murphy
2017-08-14 20:27 ` Goffredo Baroncelli
2017-08-14 6:36 ` Qu Wenruo
2017-08-14 7:43 ` Paul Jones
2017-08-14 7:46 ` Qu Wenruo
2017-08-14 12:32 ` Christoph Anton Mitterer
2017-08-14 12:58 ` Qu Wenruo
2017-08-14 12:24 ` Christoph Anton Mitterer
2017-08-14 14:23 ` Austin S. Hemmelgarn
2017-08-14 15:13 ` Graham Cobb
2017-08-14 15:53 ` Austin S. Hemmelgarn
2017-08-14 16:42 ` Graham Cobb
2017-08-14 19:54 ` Christoph Anton Mitterer
2017-08-15 11:37 ` Austin S. Hemmelgarn
2017-08-15 14:41 ` Christoph Anton Mitterer
2017-08-15 15:43 ` Austin S. Hemmelgarn
2017-08-16 13:12 ` Chris Mason
2017-08-16 13:31 ` Christoph Anton Mitterer
2017-08-16 13:53 ` Austin S. Hemmelgarn
2017-08-16 14:11 ` Christoph Anton Mitterer
2017-08-16 15:07 ` Austin S. Hemmelgarn
2017-08-16 17:26 ` Peter Grandi
2017-08-16 18:19 ` David Sterba
2017-08-16 16:54 ` Peter Grandi
2017-08-16 13:56 ` Austin S. Hemmelgarn
2017-08-16 14:01 ` Qu Wenruo
2017-08-16 19:52 ` Chris Murphy
2017-08-17 6:25 ` GWB
2017-08-17 11:47 ` Austin S. Hemmelgarn
2017-08-17 19:00 ` Chris Murphy
2017-08-17 20:34 ` GWB
2017-08-16 16:44 ` Peter Grandi
2017-08-14 19:39 ` Christoph Anton Mitterer
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=CAJCQCtRGUBWD6Mw6pAiKGAPgGz+vqy3sgmbEBDETPYsxJw8G7w@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=brendan@swiftspirit.co.za \
--cc=linux-btrfs@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 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).