From: Peter Xu <peterx@redhat.com>
To: Yong Huang <yong.huang@smartx.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH] migration: Refine the convergence detection
Date: Wed, 7 Aug 2024 08:59:02 -0400 [thread overview]
Message-ID: <ZrNvltexbLK8yxTm@x1n> (raw)
In-Reply-To: <CAK9dgmYcW7C9i+KGMH1pN_QRWy_A1ZGXixi49Unt6VhaP6DVzw@mail.gmail.com>
On Wed, Aug 07, 2024 at 02:46:29PM +0800, Yong Huang wrote:
> I still think dropping the dirty_rate_high_cnt is a refinement. If migration
> has a precise detection of convergence, what do you think of it?
Maybe; I don't think I thought through those yet.. If so that'll make
sense to be based on the sync change first, then we can have a parameter
(doesn't sound like a cap on its own) for keeping the old auto-converge,
and pile new logics there.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2024-08-07 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 11:39 [PATCH] migration: Refine the convergence detection Hyman Huang
2024-07-30 20:01 ` Peter Xu
2024-08-05 7:03 ` Yong Huang
2024-08-06 16:45 ` Peter Xu
2024-08-07 6:46 ` Yong Huang
2024-08-07 12:59 ` Peter Xu [this message]
2024-08-07 15:43 ` Yong Huang
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=ZrNvltexbLK8yxTm@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=yong.huang@smartx.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).