From: Eric Blake <eblake@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] add-cow file format
Date: Wed, 01 Aug 2012 07:57:59 -0600 [thread overview]
Message-ID: <501935E7.8000607@redhat.com> (raw)
In-Reply-To: <1343753510-24661-3-git-send-email-wdongxu@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On 07/31/2012 10:51 AM, Dong Xu Wang wrote:
> This is the implementation code for add-cow file format. Because image_file
> might be very huge, then we can't read entire bitmap into memory, we must use
> a cache. Since qcow-cache.c has implemted cache code, we can create our cache
s/implemted/implemented/
> code based on it.
Just wondering if Paolo's HBitmap code for drive-mirror might be a more
efficient way to implement your caching.
>
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
> ---
> block/Makefile.objs | 1 +
> block/add-cow-cache.c | 206 +++++++++++++++++
> block/add-cow.c | 599 +++++++++++++++++++++++++++++++++++++++++++++++++
> block/add-cow.h | 101 +++++++++
> block_int.h | 2 +
Rather than adding a new implementation for code duplication, can you
refactor the existing implementation to be reusable, and update
qcow-cache.c to call into the common refactored code?
--
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: 620 bytes --]
next prev parent reply other threads:[~2012-08-01 13:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 16:51 [Qemu-devel] [PATCH 1/6 v11] docs: spec for add-cow file format Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 2/6 v11 v11] block: make some functions public Dong Xu Wang
2012-08-01 13:53 ` Eric Blake
2012-08-02 7:10 ` Dong Xu Wang
2012-08-01 14:01 ` Stefan Hajnoczi
2012-08-02 7:11 ` Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 3/6] add-cow file format Dong Xu Wang
2012-08-01 13:57 ` Eric Blake [this message]
2012-08-01 14:14 ` Stefan Hajnoczi
2012-08-01 14:21 ` Kevin Wolf
2012-08-02 7:20 ` Dong Xu Wang
2012-08-01 15:31 ` Stefan Hajnoczi
2012-08-02 7:20 ` Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 4/6 v11] add-cow: support snapshot_blkde Dong Xu Wang
2012-08-01 15:37 ` Stefan Hajnoczi
2012-08-02 7:28 ` Dong Xu Wang
2012-08-02 10:37 ` Stefan Hajnoczi
2012-07-31 16:51 ` [Qemu-devel] [PATCH 5/6 v11] add-cow: hmp and qmp interface Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 6/6 v11] add-cow: support qemu-iotests Dong Xu Wang
2012-08-01 13:51 ` [Qemu-devel] [PATCH 1/6 v11] docs: spec for add-cow file format Eric Blake
2012-08-02 7:03 ` Dong Xu Wang
2012-08-01 13:55 ` Stefan Hajnoczi
2012-08-02 7:09 ` Dong Xu Wang
2012-08-02 10:44 ` Stefan Hajnoczi
2012-08-03 5:56 ` Dong Xu Wang
2012-08-03 8:26 ` Stefan Hajnoczi
2012-08-06 2:05 ` Dong Xu Wang
-- strict thread matches above, loose matches on Subject: below --
2012-06-13 14:36 [Qemu-devel] [PATCH 1/6 v10] " Dong Xu Wang
2012-06-13 14:36 ` [Qemu-devel] [PATCH 3/6] " Dong Xu Wang
2012-06-14 11:13 ` Paolo Bonzini
2012-06-18 2:08 ` Dong Xu Wang
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=501935E7.8000607@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).