From: Eric Blake <eblake@redhat.com>
To: Chao Fan <fanc.fnst@cn.fujitsu.com>,
dgilbert@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com,
armbru@redhat.com
Cc: caoj.fnst@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
douly.fnst@cn.fujitsu.com, maozy.fnst@cn.fujitsu.com,
izumi.taku@jp.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH] Add inst_dirty_pages_rate in 'info migrate'
Date: Wed, 1 Mar 2017 08:20:36 -0600 [thread overview]
Message-ID: <6d0db5ad-983b-1eb1-571a-c6d8755bffa8@redhat.com> (raw)
In-Reply-To: <20170301081951.27363-1-fanc.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On 03/01/2017 02:19 AM, Chao Fan wrote:
> Auto-converge aims to accelerate migration by slowing down the
> generation of dirty pages. But user doesn't know how to determine the
> throttle value, so, a new item "inst-dirty-pages-rate" in "info migrate"
> would be helpful for user's determination.
>
> Signed-off-by: Chao Fan <fanc.fnst@cn.fujitsu.com>
> ---
> +++ b/qapi-schema.json
> @@ -581,6 +581,7 @@
> 'data': {'transferred': 'int', 'remaining': 'int', 'total': 'int' ,
> 'duplicate': 'int', 'skipped': 'int', 'normal': 'int',
> 'normal-bytes': 'int', 'dirty-pages-rate' : 'int',
> + 'inst-dirty-pages-rate' : 'int',
Missing documentation, including a '(since 2.9)' tag (if that's what you
are aiming for).
> 'mbps' : 'number', 'dirty-sync-count' : 'int',
> 'postcopy-requests' : 'int' } }
>
>
--
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: 604 bytes --]
prev parent reply other threads:[~2017-03-01 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 8:19 [Qemu-devel] [PATCH] Add inst_dirty_pages_rate in 'info migrate' Chao Fan
2017-03-01 8:39 ` no-reply
2017-03-01 14:20 ` 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=6d0db5ad-983b-1eb1-571a-c6d8755bffa8@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=dgilbert@redhat.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=maozy.fnst@cn.fujitsu.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).