From: Eric Blake <eblake@redhat.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 7/7] migration: Add dirty_pages_rate to query migrate output
Date: Mon, 13 Aug 2012 10:49:51 -0600 [thread overview]
Message-ID: <5029302F.2080503@redhat.com> (raw)
In-Reply-To: <87y5liwzg8.fsf@elfo.mitica>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
On 08/13/2012 10:04 AM, Juan Quintela wrote:
>>> +# @dirty-pages-rate: number of pages dirtied by second by the
>>> +# guest. (since 1.2)
>>
>> Since HMP only prints this stat when it is non-zero, should this field
>> be marked optional? Then again, once you have dirty page tracking, I
>> suspect this would never be zero (or even showing an explicit zero would
>> help detect stalls).
>
> What is easier for libvirt to have here.
>
> At the beggining, this value is going to be wrong/cero. I can:
> - not print it until it is != 0
> - print a big enough number )
> - make it optional? I guess this would alse be more difficult for
> libvirt.
> - put your good idea here?
I see your point about querying early enough that there is not yet
enough data to have a good estimate. In that case, either outputting 0
or omitting the field will do the trick. Libvirt already has to support
older qemu that always omitted the field, and it is a one-liner code
addition in libvirt to say that if the field is omitted, treat it like
'0'. I'm not even quite sure what libvirt will be able to do with this
number; libvirt made some unfortunate API decisions where migration
statistics are exposed to the user in a hard-coded struct
(virDomainJobInfo), and since we didn't allow for the struct to grow
without breaking ABI, exposing additional information would require a
new libvirt API. So don't let libvirt hold up the inclusion of this
useful information on the qemu side of things.
Maybe another option would be to return [U]INT_MAX when there is not
enough data to yet provide a valid number, where having a non-zero value
at least lets people know that the stat will be available in a later call.
--
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-13 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 10:50 [Qemu-devel] [RFC 0/7] Migration stats Juan Quintela
2012-08-13 10:50 ` [Qemu-devel] [PATCH 1/7] migration: move total_time from ram stats to migration info Juan Quintela
2012-08-13 14:32 ` Eric Blake
2012-08-13 10:50 ` [Qemu-devel] [PATCH 2/7] migration: store end_time in a local variable Juan Quintela
2012-08-13 15:01 ` Eric Blake
2012-08-13 10:50 ` [Qemu-devel] [PATCH 3/7] migration: print total downtime for final phase of migration Juan Quintela
2012-08-13 15:02 ` Eric Blake
2012-08-13 15:03 ` Eric Blake
2012-08-13 19:36 ` Luiz Capitulino
2012-08-13 10:50 ` [Qemu-devel] [PATCH 4/7] migration: rename expected_time to expected_downtime Juan Quintela
2012-08-13 15:05 ` Eric Blake
2012-08-13 10:50 ` [Qemu-devel] [PATCH 5/7] migration: export migration_get_current() Juan Quintela
2012-08-13 15:06 ` Eric Blake
2012-08-13 10:50 ` [Qemu-devel] [PATCH 6/7] migration: print expected downtime in info migrate Juan Quintela
2012-08-13 15:08 ` Eric Blake
2012-08-13 10:50 ` [Qemu-devel] [PATCH 7/7] migration: Add dirty_pages_rate to query migrate output Juan Quintela
2012-08-13 15:12 ` Eric Blake
2012-08-13 16:04 ` Juan Quintela
2012-08-13 16:49 ` Eric Blake [this message]
2012-08-13 14:59 ` [Qemu-devel] [RFC 0/7] Migration stats Eric Blake
2012-08-13 15:08 ` Juan Quintela
2012-08-13 15:14 ` Eric Blake
2012-08-13 19:47 ` Luiz Capitulino
2012-08-16 10:25 ` Qunfang Zhang
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=5029302F.2080503@redhat.com \
--to=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).