From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bob Liu <bob.liu@oracle.com>
Cc: "Juergen Gross" <jgross@suse.com>,
xen-devel@lists.xen.org, Paul.Durrant@citrix.com,
david.vrabel@citrix.com, Ian.Jackson@citrix.com,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [RFC PATCH] Data integrity extension support for xen-block
Date: Mon, 11 Apr 2016 11:04:38 -0400 [thread overview]
Message-ID: <20160411150438.GB19841@char.us.oracle.com> (raw)
In-Reply-To: <57078442.3040901@oracle.com>
> * A filesystem in Guest that is integrity-aware can prepare I/Os with metadata attached.
> * Filesystems in Guest are capable of transferring metadata from user space.
> Those metadata get lost if we don't pass them through in blkfront.
>
> You may have a look at:
> [1] http://lwn.net/Articles/280023/
> [2] https://www.kernel.org/doc/Documentation/block/data-integrity.txt
And Google for SCSI DIF/DIX which can give you some ideas. There is also
this slide-deck: https://oss.oracle.com/~mkp/docs/ols2008-slides.pdf
Also note that some devices (like NVMe) also implement some of this:
http://www.flashmemorysummit.com/English/Collaterals/Proceedings/2014/20140804_Seminar_F_Busch.pdf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-11 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 10:00 [RFC PATCH] Data integrity extension support for xen-block Bob Liu
2016-04-07 15:32 ` Ian Jackson
2016-04-07 15:55 ` Juergen Gross
2016-04-08 1:24 ` Bob Liu
2016-04-08 4:04 ` Juergen Gross
2016-04-08 9:44 ` Roger Pau Monné
2016-04-08 10:13 ` Bob Liu
2016-04-08 13:42 ` Ian Jackson
2016-04-11 15:04 ` Konrad Rzeszutek Wilk [this message]
2016-04-08 14:16 ` David Vrabel
2016-04-08 14:20 ` Ian Jackson
2016-04-08 14:32 ` David Vrabel
2016-04-11 12:32 ` Bob Liu
2016-04-13 12:22 ` Bob Liu
2016-04-13 13:19 ` Ian Jackson
2016-04-13 14:43 ` Juergen Gross
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=20160411150438.GB19841@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=bob.liu@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).