From: Eric Blake <eblake@redhat.com>
To: benoit.canet@gmail.com
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com,
stefanha@gmail.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
"Benoît Canet" <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [PATCH V3 1/3] block: create bdrv_get_backing_file_ancestors_count()
Date: Wed, 25 Jul 2012 10:27:09 -0600 [thread overview]
Message-ID: <50101E5D.30808@redhat.com> (raw)
In-Reply-To: <1343219765-12297-2-git-send-email-benoit@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]
On 07/25/2012 06:36 AM, benoit.canet@gmail.com wrote:
> From: Benoît Canet <benoit@irqsave.net>
>
> Create bdrv_get_backing_file_ancestors_count() in order to be
> able to show in QMP and HMP how many ancestors backing an image a
> block device have.
>
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---
> block.c | 13 +++++++++++++
> block.h | 1 +
> 2 files changed, 14 insertions(+)
>
> diff --git a/block.c b/block.c
> index ce7eb8f..03e0860 100644
> --- a/block.c
> +++ b/block.c
> @@ -2754,6 +2754,19 @@ BlockDriverState *bdrv_find_backing_image(BlockDriverState *bs,
> return NULL;
> }
>
> +int bdrv_get_backing_file_ancestors_count(BlockDriverState *bs)
> +{
> + if (!bs->drv) {
> + return 0;
> + }
> +
> + if (!bs->backing_hd) {
> + return 0;
> + }
> +
> + return 1 + bdrv_get_backing_file_ancestors_count(bs->backing_hd);
Is there any risk of stack overflow for a hugely nested setup? Then
again, I suspect you are going to run into other issues if you are
nested that deeply, before this recursion could cause overflow worth
worrying about.
This is an O(n) operation; is it worth storing the nesting depth as part
of a BlockDriverState to turn it into an O(1) operation? That is, you
already have to do the O(n) traversal once when originally opening the
chain, so why not have opening the chain populate a struct member with
how deep the opening went, so that all future queries can just return
that struct member. Of course, you then run into the issue that
operations that change the depth (snapshot, block streaming, and the
proposed block commit) would then be O(n) to adjust the counts of every
member of the chain, instead of O(1) because the count is computed on
the fly. Just food for thought, and not a technical reason requiring
you to rewrite the patch unless you really like the idea.
--
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-07-25 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:36 [Qemu-devel] [PATCH V3 0/3] Show backing file ancestors count in HMP benoit.canet
2012-07-25 12:36 ` [Qemu-devel] [PATCH V3 1/3] block: create bdrv_get_backing_file_ancestors_count() benoit.canet
2012-07-25 16:27 ` Eric Blake [this message]
2012-07-25 17:19 ` Benoît Canet
2012-07-25 12:36 ` [Qemu-devel] [PATCH V3 2/3] block: Use bdrv_get_backing_file_ancestors_count() benoit.canet
2012-07-25 16:37 ` Eric Blake
2012-07-25 17:20 ` Benoît Canet
2012-07-25 16:39 ` Eric Blake
2012-07-25 17:21 ` Benoît Canet
2012-07-25 12:36 ` [Qemu-devel] [PATCH V3 3/3] hmp: show the backing file ancestors count benoit.canet
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=50101E5D.30808@redhat.com \
--to=eblake@redhat.com \
--cc=benoit.canet@gmail.com \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).