From: "Benoît Canet" <benoit@irqsave.net>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com,
stefanha@linux.vnet.ibm.com, "Benoît Canet" <benoit@irqsave.net>
Subject: [Qemu-devel] [partial RFC 1/2] qcow2: modify spec for deduplication
Date: Thu, 27 Sep 2012 16:29:57 +0200 [thread overview]
Message-ID: <1348756198-10845-2-git-send-email-benoit@irqsave.net> (raw)
In-Reply-To: <1348756198-10845-1-git-send-email-benoit@irqsave.net>
---
docs/specs/qcow2.txt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/specs/qcow2.txt b/docs/specs/qcow2.txt
index 36a559d..e8bc189 100644
--- a/docs/specs/qcow2.txt
+++ b/docs/specs/qcow2.txt
@@ -80,7 +80,10 @@ in the description of a field.
tables to repair refcounts before accessing the
image.
- Bits 1-63: Reserved (set to 0)
+ Bit 1: Deduplication bit. If this bit is set then
+ deduplication is used on this image.
+
+ Bits 2-63: Reserved (set to 0)
80 - 87: compatible_features
Bitmask of compatible features. An implementation can
@@ -116,6 +119,7 @@ be stored. Each extension has a structure like the following:
0x00000000 - End of the header extension area
0xE2792ACA - Backing file format name
0x6803f857 - Feature name table
+ 0xCD8E819B - Deduplication table offset and length
other - Unknown header extension, can be safely
ignored
--
1.7.10.4
next prev parent reply other threads:[~2012-09-27 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:29 [Qemu-devel] [partial RFC 0/2] QCow2 deduplication write mechanism Benoît Canet
2012-09-27 14:29 ` Benoît Canet [this message]
2012-09-27 15:02 ` [Qemu-devel] [partial RFC 1/2] qcow2: modify spec for deduplication Eric Blake
2012-09-27 14:29 ` [Qemu-devel] [partial RFC 2/2] qcow2: Deduplication write mechanism Benoît Canet
2012-09-27 15:58 ` [Qemu-devel] [partial RFC 0/2] QCow2 deduplication " Avi Kivity
2012-09-27 17:11 ` Benoît Canet
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=1348756198-10845-2-git-send-email-benoit@irqsave.net \
--to=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).