From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-block@nongnu.org, armbru@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [RFC] QMP design: Fixing query-block and friends
Date: Fri, 30 Jun 2017 16:22:11 +0200 [thread overview]
Message-ID: <20170630142211.GB4776@noname.redhat.com> (raw)
In-Reply-To: <w51shihd3y2.fsf@maestria.local.igalia.com>
Am 30.06.2017 um 15:01 hat Alberto Garcia geschrieben:
> On Tue 27 Jun 2017 06:31:45 PM CEST, Kevin Wolf wrote:
> > * Speaking of recursion: ImageInfo recursively includes information
> > about all images in the backing chain. This is what makes the output
> > of query-named-block-nodes so redundant. It is also inconsistent
> > because the runtime information (BlockInfo/BlockDeviceInfo) isn't
> > recursive.
>
> I've also been told of cases where a query-block command on a VM with a
> very large amount of images in all backing chains would slow down the
> guest because of this recursion.
>
> I haven't been able to reproduce this problem myself, but being able to
> see only the devices seen by the guest (as opposed to the complete
> graph) seems like a good idea.
I think the information only really becomes redundant if you use
query-named-block-nodes because then you list every backing file node
and each of them contains the recursive information.
With query-block, you start at the top and include the information for
each image in the backing file chain only once. If we did indeed have a
problem there, that might mean that we do in fact need filtering to
reduce the overhead. But I don't think any of the information involves
any I/O to get, so it seems unlikely to me that this would make a big
difference.
Kevin
next prev parent reply other threads:[~2017-06-30 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 16:31 [Qemu-devel] [RFC] QMP design: Fixing query-block and friends Kevin Wolf
2017-06-27 16:46 ` Eric Blake
2017-06-28 7:10 ` Markus Armbruster
2017-06-28 10:06 ` Kevin Wolf
2017-06-28 11:59 ` Markus Armbruster
2017-06-27 18:24 ` [Qemu-devel] [Qemu-block] " John Snow
2017-06-28 7:15 ` Markus Armbruster
2017-06-28 16:00 ` John Snow
2017-06-29 7:23 ` Markus Armbruster
2017-07-05 14:53 ` Stefan Hajnoczi
2017-06-30 13:01 ` Alberto Garcia
2017-06-30 14:22 ` Kevin Wolf [this message]
2017-06-30 14:30 ` Alberto Garcia
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=20170630142211.GB4776@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).