From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: Eric Blake <eblake@redhat.com>
Cc: quintela@redhat.com, dgilbert@redhat.com, qemu-devel@nongnu.org,
berrange@redhat.com, caoj.fnst@cn.fujitsu.com,
douly.fnst@cn.fujitsu.com, maozy.fnst@cn.fujitsu.com,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH] Output dirty-bytes-rate instead of dirty-pages-rate
Date: Tue, 14 Mar 2017 23:40:28 +0800 [thread overview]
Message-ID: <20170314154028.GA10433@localhost.localdomain> (raw)
In-Reply-To: <7110d95e-d500-a1ee-c590-2f44460d9881@redhat.com>
On Tue, Mar 14, 2017 at 09:54:34AM -0500, Eric Blake wrote:
>On 03/14/2017 05:27 AM, Chao Fan wrote:
>> In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> It's also better for other tools to determine the cpu throttle
>> value in different architecture.
>>
>> Signed-off-by: Chao Fan <fanc.fnst@cn.fujitsu.com>
>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>> ---
>
>In addition to the (good) comments you've gotten on not breaking
>existing fields, and the choice between a single new field giving the
>page size (with all fields favoring pages) or lots of new fields giving
>bytes, I have another comment:
>
>> @@ -575,12 +572,15 @@
>> # @postcopy-requests: The number of page requests received from the destination
>> # (since 2.7)
>> #
>> +# @dirty-bytes-rate: how many bytes dirtied by second by the
>> +# guest (since 2.9)
>
>You've missed soft freeze. Is this really bug-fix quality to be adding
>it into the release this late in the game for 2.9, or should it be
>deferred to 2.10?
Ok, I will change it.
Many thanks for your help.
Thanks,
Chao Fan
>
>And while this is just a new field to an existing command, rather than a
>new command entirely, it's also worth thinking about Markus' edict for
>testsuite coverage:
>https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg00296.html
>
>--
>Eric Blake eblake redhat com +1-919-301-3266
>Libvirt virtualization library http://libvirt.org
>
prev parent reply other threads:[~2017-03-14 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 10:27 [Qemu-devel] [PATCH] Output dirty-bytes-rate instead of dirty-pages-rate Chao Fan
2017-03-14 10:45 ` Daniel P. Berrange
2017-03-14 11:51 ` Chao Fan
2017-03-14 12:29 ` Juan Quintela
2017-03-14 12:37 ` Daniel P. Berrange
2017-03-14 13:20 ` Chao Fan
2017-03-15 4:13 ` Chao Fan
2017-03-15 9:42 ` Daniel P. Berrange
2017-03-14 13:33 ` Chao Fan
2017-03-14 14:54 ` Eric Blake
2017-03-14 15:40 ` Chao Fan [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=20170314154028.GA10433@localhost.localdomain \
--to=fanc.fnst@cn.fujitsu.com \
--cc=berrange@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=dgilbert@redhat.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=eblake@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.