From: Avi Kivity <avi@redhat.com>
To: "Benoît Canet" <benoit@irqsave.net>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [partial RFC 0/2] QCow2 deduplication write mechanism
Date: Thu, 27 Sep 2012 17:58:11 +0200 [thread overview]
Message-ID: <50647793.7000106@redhat.com> (raw)
In-Reply-To: <1348756198-10845-1-git-send-email-benoit@irqsave.net>
On 09/27/2012 04:29 PM, Benoît Canet wrote:
> This patchset introduce a partial implementation of a deduplication mechanism
> for QCow2.
> This patchset layout the disk format changes in the qcow2 spec and
> provide a partial implementation of the write mechanisms.
>
> Albeit being partial this is posted to get an early feedback and
> see if things are on track.
If I understood correctly, this does cluster-level dedup within a qcow2
image.
What is the motivation here? Reduce space usage if a guest copies files
internally?
Why use cluster granularity? If the guest uses smaller granularity, it
will misalign the data wrt cluster boundaries, and deduplication will fail.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-27 15:58 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 ` [Qemu-devel] [partial RFC 1/2] qcow2: modify spec for deduplication Benoît Canet
2012-09-27 15:02 ` 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 ` Avi Kivity [this message]
2012-09-27 17:11 ` [Qemu-devel] [partial RFC 0/2] QCow2 deduplication " 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=50647793.7000106@redhat.com \
--to=avi@redhat.com \
--cc=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).