From: Fam Zheng <famz@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] block: allow commit active as top
Date: Mon, 22 Jul 2013 15:05:24 +0800 [thread overview]
Message-ID: <20130722070524.GB1992@T430s.redhat.com> (raw)
In-Reply-To: <51ECD49A.5050104@linux.vnet.ibm.com>
On Mon, 07/22 14:43, Wenchao Xia wrote:
> 于 2013-7-22 11:46, Fam Zheng 写道:
> > Previously live commit of active block device is not supported, this series
> > implements it and updates corresponding qemu-iotests cases.
> >
> > Please see commit messages for implementation details.
> >
> > Fam Zheng (2):
> > block: allow live commit of active image
> > qemu-iotests: update test cases for commit active
> >
> > block.c | 102 ++++++++++---------------------
> > block/commit.c | 160 +++++++++++++++++++++++++------------------------
> > include/block/block.h | 5 +-
> > tests/qemu-iotests/040 | 68 ++++++++-------------
> > 4 files changed, 141 insertions(+), 194 deletions(-)
> >
> I have thought the commit with top issue before, a question comes to
> me: what is the relationship with block-stream?
>
> for example:
> base->mid->top
>
> you can block-stream mid to top(if I remember correctly), result is:
> base->(mid+top)
>
> with this patch, you can block-commit top to mid, result is:
> base->(mod+top)
>
> it seems the function is duplicated. Maybe you can raise another
> good user case. I must say it may help user to do every thing
> with block-commit, but if you find it is too much to make it work,
> maybe you can postpond it, since block-stream is available.
>
Of course, you can either merge 'top' into 'mid', or merge 'mid' into
'top', you always get sum of them. However if 'mid' is very large while
you only allocated a few clusters in 'top', block-stream is not very nice
to use: you need to copy the whole 'mid' to 'top'. But committing 'top'
back to 'mid', if it has no other children, will be much faster.
--
Fam
prev parent reply other threads:[~2013-07-22 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 3:46 [Qemu-devel] [PATCH 0/2] block: allow commit active as top Fam Zheng
2013-07-22 3:46 ` [Qemu-devel] [PATCH 1/2] block: allow live commit of active image Fam Zheng
2013-07-22 6:34 ` Paolo Bonzini
2013-07-22 6:48 ` Fam Zheng
2013-07-22 11:07 ` Paolo Bonzini
2013-07-23 2:03 ` Fam Zheng
2013-07-23 11:13 ` Paolo Bonzini
2013-07-22 3:46 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: update test cases for commit active Fam Zheng
2013-07-22 6:43 ` [Qemu-devel] [PATCH 0/2] block: allow commit active as top Wenchao Xia
2013-07-22 7:05 ` Fam Zheng [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=20130722070524.GB1992@T430s.redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiawenc@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).