From: Alberto Bertogli <albertito@blitiri.com.ar>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org, agk@redhat.com, neilb@suse.de
Subject: Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
Date: Thu, 21 May 2009 16:17:04 -0300 [thread overview]
Message-ID: <20090521191704.GX1376@blitiri.com.ar> (raw)
In-Reply-To: <87f94c370905211117y13758f72i2ea113c9c6771061@mail.gmail.com>
On Thu, May 21, 2009 at 02:17:58PM -0400, Greg Freemyer wrote:
> On Thu, May 21, 2009 at 12:13 PM, Alberto Bertogli
> <albertito@blitiri.com.ar> wrote:
> > I'm writing this device mapper target that stores checksums on writes and
> > verifies them on reads.
>
> I have not looked at your patch, but does this tie into the integrity
> logic that was added to mainline a few months ago?
At the moment it has no relation, but making dm-csum devices register with the
bio integrity extensions is on my to-do list, and the on-disk format already
reserves 32 bits for every 512-byte sector for tagging purposes.
Thanks,
Alberto
next prev parent reply other threads:[~2009-05-21 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 16:13 [RFC PATCH] dm-csum: A new device mapper target that checks data integrity Alberto Bertogli
2009-05-21 18:17 ` Greg Freemyer
2009-05-21 19:17 ` Alberto Bertogli [this message]
2009-05-25 12:22 ` Goswin von Brederlow
2009-05-25 17:46 ` Alberto Bertogli
2009-05-26 10:33 ` Goswin von Brederlow
2009-05-26 12:52 ` Alberto Bertogli
2009-05-28 19:29 ` Goswin von Brederlow
2009-06-26 7:26 ` SandeepKsinha
2009-06-26 8:50 ` SandeepKsinha
2009-06-26 22:36 ` Alberto Bertogli
2009-06-26 22:53 ` Alan Cox
2009-06-28 0:34 ` Neil Brown
2009-06-28 15:30 ` Alberto Bertogli
2009-06-28 22:59 ` Goswin von Brederlow
2009-05-26 19:48 ` [RFC PATCH v2] " Alberto Bertogli
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=20090521191704.GX1376@blitiri.com.ar \
--to=albertito@blitiri.com.ar \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=greg.freemyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).