From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Avi Kivity <avi@redhat.com>
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 19:11:58 +0200 [thread overview]
Message-ID: <20120927171157.GA4407@irqsave.net> (raw)
In-Reply-To: <50647793.7000106@redhat.com>
> If I understood correctly, this does cluster-level dedup within a qcow2
> image.
yes
> What is the motivation here? Reduce space usage if a guest copies files
> internally?
First use case is people using LXC, OpenVZ or chroot inside vms they rent
to their "cloud" provider.
Second use case is applications generating duplicates blocks.
A well known CAD software does this and on a filer doing deduplication
on 4KB blocks the dedup ratio is around five.
>
> Why use cluster granularity? If the guest uses smaller granularity, it
> will misalign the data wrt cluster boundaries, and deduplication will fail.
Using cluster granularity would allow to use the qcow2 refcount and l1/l2
tables to track duplicated blocks.
The patch embryo does read the missing data if given data is misaligned.
To avoid hurting performance using a smaller cluster size with the adequate
changes in qcow2 may help.
Regards
Benoît
prev parent reply other threads:[~2012-09-27 17:12 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 ` [Qemu-devel] [partial RFC 0/2] QCow2 deduplication " Avi Kivity
2012-09-27 17:11 ` Benoît Canet [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=20120927171157.GA4407@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=avi@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.