From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@redhat.com>
Cc: Uri Lublin <uril@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ram_save_live: add a no-progress convergence rule
Date: Tue, 19 May 2009 13:09:58 -0500 [thread overview]
Message-ID: <4A12F5F6.2010003@codemonkey.ws> (raw)
In-Reply-To: <20090519144101.GA16372@shell.devel.redhat.com>
Glauber Costa wrote:
> Another possibility is for the management tool to increase the bandwidth for
> little periods if it perceives that no progress is being made.
>
> Anyhow, I completely agree that we should not introduce this in qemu.
>
> However, maybe we could augment our "info migrate" to provide more info about
> the internal state of migration, so the mgmt tool can take a more informed
> decision?
>
Yes, I've also suggested this before. I'm willing to expose just about
any metric that makes sense. We need to be careful about not exposing
implementation details, but things like iteration count, last working
set size, average working set size, etc. should all be relatively stable
metrics even if the implementation changes.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-19 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 11:09 [Qemu-devel] [PATCH] ram_save_live: add a no-progress convergence rule Uri Lublin
2009-05-19 13:00 ` Anthony Liguori
2009-05-19 14:41 ` Glauber Costa
2009-05-19 14:59 ` Dor Laor
2009-05-19 15:09 ` Glauber Costa
2009-05-19 18:17 ` Anthony Liguori
2009-05-20 16:56 ` Uri Lublin
2009-05-20 17:28 ` Blue Swirl
2009-05-20 17:34 ` Uri Lublin
2009-05-19 18:19 ` Anthony Liguori
2009-05-19 18:15 ` Anthony Liguori
2009-05-20 17:17 ` Uri Lublin
2009-05-19 18:09 ` Anthony Liguori [this message]
2009-05-20 17:25 ` Uri Lublin
2009-05-20 17:15 ` Daniel P. Berrange
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=4A12F5F6.2010003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=glommer@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=uril@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).