From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit.canet@gmail.com>
Cc: kwolf@redhat.com, "Benoît Canet" <benoit@irqsave.net>,
qemu-devel@nongnu.org, lcapitulino@redhat.com,
pbonzini@redhat.com, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V6 0/3] Show backing file depth in HMP and QMP
Date: Thu, 02 Aug 2012 14:52:02 -0600 [thread overview]
Message-ID: <501AE872.8010106@redhat.com> (raw)
In-Reply-To: <1343895769-21255-1-git-send-email-benoit@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On 08/02/2012 02:22 AM, Benoît Canet wrote:
> In some setups many backing files and snapshot are chained.
> This lead to the formation of huge trees of snapshots all depending
> on a common ancestor.
>
> Hence if something bad happen to this common ancestor all the snapshot
> of the tree will be broken.
>
> This patch add an easy way for the user to monitor backing file depth
> and take the good decision (streaming).
>
No further findings from me, so series:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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 --]
prev parent reply other threads:[~2012-08-02 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 8:22 [Qemu-devel] [PATCH V6 0/3] Show backing file depth in HMP and QMP Benoît Canet
2012-08-02 8:22 ` [Qemu-devel] [PATCH V6 1/3] block: create bdrv_get_backing_file_depth() Benoît Canet
2012-08-02 8:22 ` [Qemu-devel] [PATCH V6 2/3] block: Use bdrv_get_backing_file_depth() Benoît Canet
2012-08-02 8:22 ` [Qemu-devel] [PATCH V6 3/3] hmp: show the backing file depth Benoît Canet
2012-08-02 20:47 ` [Qemu-devel] [PATCH V6 0/3] Show backing file depth in HMP and QMP Luiz Capitulino
2012-08-02 20:52 ` 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=501AE872.8010106@redhat.com \
--to=eblake@redhat.com \
--cc=benoit.canet@gmail.com \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=lcapitulino@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).