From: Eric Blake <eblake@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Fam Zheng <famz@redhat.com>,
wdongxu@cn.ibm.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V20 0/7] add-cow file format
Date: Tue, 23 Feb 2016 06:33:22 -0700 [thread overview]
Message-ID: <56CC5FA2.80903@redhat.com> (raw)
In-Reply-To: <1377446780-15360-1-git-send-email-wdongxu@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Reviving an old thread for discussion purposes:
On 08/25/2013 10:06 AM, Dong Xu Wang wrote:
> It will introduce a new file format: add-cow.
>
> The add-cow file format makes it possible to perform copy-on-write on top of
> a raw disk image. When we know that no backing file clusters remain visible
> (e.g. we have streamed the entire image and copied all data from the backing
> file), then it is possible to discard the add-cow file and use the raw image
> file directly.
>
> This feature adds the copy-on-write feature to raw files (which cannot support
> it natively) while allowing us to get full performance again later when we no
> longer need copy-on-write.
Lately there has been discussion about a new external bitmap file
format. I suspect everything in that conversation will make it possible
to do anything that was planned by this (now-abandoned) series. But
knowing all the use cases may help make sure we consider all the design
aspects for what is needed if we track bitmaps of raw files in their own
file format.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2016-02-23 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 16:06 [Qemu-devel] [PATCH V20 0/7] add-cow file format Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 1/8] docs: document for " Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 2/8] make path_has_protocol non static Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 3/8] qed_read_string to bdrv_read_string Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 4/8] rename qcow2_cache functions to block_cache Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 5/8] move qcow2-cache.c to block-cache.c Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 6/8] Make block-cache.c be common interface Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 7/8] add-cow file format core code Dong Xu Wang
2013-08-25 16:06 ` [Qemu-devel] [PATCH V20 8/8] qemu-iotests: add add-cow iotests support Dong Xu Wang
2016-02-23 13:33 ` Eric Blake [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=56CC5FA2.80903@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wdongxu@cn.ibm.com \
--cc=wdongxu@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).