From: Nikko <nikko.he@oracle.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: One question about btrfs
Date: Wed, 13 Oct 2010 10:56:43 +0800 [thread overview]
Message-ID: <4CB51FEB.8070006@oracle.com> (raw)
In-Reply-To: <yq17hhnpclc.fsf@sermon.lab.mkp.net>
On 10/13/10 01:03 AM, Martin K. Petersen wrote:
>>>>>> "Nikko" == Nikko<nikko.he@oracle.com> writes:
>>>>>>
> Nikko> I have a question about btrfs, have you people integrated Oracle
> Nikko> DIX/T10 DIF into btrfs?
>
> Not yet. Right now btrfs relies on the block layer to add the integrity
> metadata.
>
>
> Nikko> If no, do you plan to do that? And what's the reason?
>
> Yes, the reason being that we want applications to be able to pass the
> integrity metadata down from userland.
>
>
Hi Martin,
Thanks for the guide!
Regards,
Nikko
prev parent reply other threads:[~2010-10-13 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 8:29 One question about btrfs Nikko
[not found] ` <yq17hhnpclc.fsf@sermon.lab.mkp.net>
2010-10-13 2:56 ` Nikko [this message]
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=4CB51FEB.8070006@oracle.com \
--to=nikko.he@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.petersen@oracle.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).