From: Christoph Hellwig <hch@infradead.org>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Subject: Re: Support for data CRC
Date: Sun, 10 Sep 2017 23:37:29 -0700 [thread overview]
Message-ID: <20170911063729.GA10489@infradead.org> (raw)
In-Reply-To: <20170910195026.7ftxcgmwyri5a5fz@breakpoint.cc>
On Sun, Sep 10, 2017 at 09:50:27PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-22 23:19:31 [-0700], Christoph Hellwig wrote:
> > as part of the reflink feature. These out of place writes are
> > a requirement to implement data checksums, as otherwise your data
> > and checksum can not be updated atomically. Everything else is
> > beyond that at this point is vapourware. We'd have to decided
> So using the journal for atomic updates doesn't work then. Which means
> fragmentation unavoidable.
Well, in theory you could also do data journalling - but in the end
out of place writes are probably going to be more efficient, and at
least for XFS also area already implemented.
next prev parent reply other threads:[~2017-09-11 6:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:04 Support for data CRC Sebastian Andrzej Siewior
2017-08-21 19:52 ` Chris Murphy
2017-08-22 11:10 ` Sebastian Andrzej Siewior
2017-08-22 22:37 ` Chris Murphy
2017-09-10 19:43 ` Testing dm-integrity (WAS: Re: Support for data CRC) Sebastian Andrzej Siewior
2017-09-10 20:06 ` Milan Broz
2017-09-11 6:38 ` Sebastian Andrzej Siewior
2017-09-11 23:44 ` Mikulas Patocka
2017-08-21 23:02 ` Support for data CRC Dave Chinner
2017-08-22 5:51 ` Christoph Hellwig
2017-08-22 11:13 ` Sebastian Andrzej Siewior
2017-08-23 6:19 ` Christoph Hellwig
2017-09-10 19:50 ` Sebastian Andrzej Siewior
2017-09-11 6:37 ` Christoph Hellwig [this message]
2017-09-11 6:52 ` Dave Chinner
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=20170911063729.GA10489@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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