From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: qemu-devel@nongnu.org, Mao Zhongyi <maozhongyi@cmss.chinamobile.com>
Subject: Re: [PATCH] monitor/hmp-cmds: add units for mirate_parameters.
Date: Fri, 27 Mar 2020 11:28:14 +0000 [thread overview]
Message-ID: <20200327112814.GD2786@work-vm> (raw)
In-Reply-To: <20200327092951.bu4ju7rh53ig5t3l@steredhat>
* Stefano Garzarella (sgarzare@redhat.com) wrote:
> Hi Mao,
>
> On Fri, Mar 27, 2020 at 03:32:10PM +0800, Mao Zhongyi wrote:
> > When running:
> > (qemu) info migrate_parameters
> > announce-initial: 50 ms
> > announce-max: 550 ms
> > announce-step: 100 ms
> > compress-wait-thread: on
> > ...
> > max-bandwidth: 33554432 bytes/second
> > downtime-limit: 300 milliseconds
> > x-checkpoint-delay: 20000
> > ...
> > xbzrle-cache-size: 67108864
> >
> > add units for the parameters 'x-checkpoint-delay' and
> > 'xbzrle-cache-size', it's easier to read.
> >
> > Signed-off-by: Mao Zhongyi <maozhongyi@cmss.chinamobile.com>
> > ---
> > monitor/hmp-cmds.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/monitor/hmp-cmds.c b/monitor/hmp-cmds.c
> > index 2a900a528a..8d22f96e57 100644
> > --- a/monitor/hmp-cmds.c
> > +++ b/monitor/hmp-cmds.c
> > @@ -440,7 +440,7 @@ void hmp_info_migrate_parameters(Monitor *mon, const QDict *qdict)
> > MigrationParameter_str(MIGRATION_PARAMETER_DOWNTIME_LIMIT),
> > params->downtime_limit);
> > assert(params->has_x_checkpoint_delay);
> > - monitor_printf(mon, "%s: %u\n",
> > + monitor_printf(mon, "%s: %u" " milliseconds\n",
> ^
> here we can remove the space and use a single string "%s: %u milliseconds\n"
Yes.
> I've noticed that we use both ms or milliseconds, if you want to clean up in a
> separate patch, maybe we could use one of these everywhere. (I vote for 'ms')
I do prefer 'ms', however we do seem to just use milliseconds in
info migrate
so we should probably stick to it.
Dave
> Thanks,
> Stefano
>
> > MigrationParameter_str(MIGRATION_PARAMETER_X_CHECKPOINT_DELAY),
> > params->x_checkpoint_delay);
> > assert(params->has_block_incremental);
> > @@ -453,7 +453,7 @@ void hmp_info_migrate_parameters(Monitor *mon, const QDict *qdict)
> > monitor_printf(mon, "%s: %s\n",
> > MigrationParameter_str(MIGRATION_PARAMETER_MULTIFD_COMPRESSION),
> > MultiFDCompression_str(params->multifd_compression));
> > - monitor_printf(mon, "%s: %" PRIu64 "\n",
> > + monitor_printf(mon, "%s: %" PRIu64 " bytes\n",
> > MigrationParameter_str(MIGRATION_PARAMETER_XBZRLE_CACHE_SIZE),
> > params->xbzrle_cache_size);
> > monitor_printf(mon, "%s: %" PRIu64 "\n",
> > --
> > 2.17.1
> >
> >
> >
> >
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-03-27 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:32 [PATCH] monitor/hmp-cmds: add units for mirate_parameters Mao Zhongyi
2020-03-27 9:29 ` Stefano Garzarella
2020-03-27 11:28 ` Dr. David Alan Gilbert [this message]
2020-03-27 13:12 ` Stefano Garzarella
2020-03-27 13:21 ` Dr. David Alan Gilbert
2020-03-27 16:09 ` maozy
2020-03-27 13:02 ` Eric Blake
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=20200327112814.GD2786@work-vm \
--to=dgilbert@redhat.com \
--cc=maozhongyi@cmss.chinamobile.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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).