From: Hyman Huang <huangy81@chinatelecom.cn>
To: Peter Xu <peterx@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Chuan Zheng <zhengchuan@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v12 0/6] support dirtyrate at the granualrity of vcpu
Date: Fri, 15 Oct 2021 10:07:00 +0800 [thread overview]
Message-ID: <78929c64-ca4d-6c6a-f371-99cd508e958a@chinatelecom.cn> (raw)
In-Reply-To: <YWjaQ80LZGvPPoeX@t490s>
在 2021/10/15 9:32, Peter Xu 写道:
> On Wed, Jun 30, 2021 at 12:01:17AM +0800, huangy81@chinatelecom.cn wrote:
>> From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
>>
>> v12
>> - adjust the order of calculating dirty rate
>> let memory_global_dirty_log_sync before calculating as
>> v11 version description.
>
> Ping for Yong. >
> Dave/Juan, any plan to review/merge this series (along with the other series of
> dirty logging)?
>
> I found it useful when I wanted to modify the program I used to generate
> constant dirty workload - this series can help me to verify the change.
>
> I still keep thinking this series is something good to have. Thanks,
the dirtyrate calculation has already been used to estimate time of live
migration in "e cloud" production of chinatelecom, it also predict the
migration success ratio, which provide valuable information for the
cloud management plane when selecting which vm should be migrated.
>
--
Best regard
Hyman Huang(黄勇)
next prev parent reply other threads:[~2021-10-15 2:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 16:01 [PATCH v12 0/6] support dirtyrate at the granualrity of vcpu huangy81
2021-06-29 16:01 ` [PATCH v12 1/6] KVM: introduce dirty_pages and kvm_dirty_ring_enabled huangy81
2021-06-29 16:01 ` [PATCH v12 2/6] memory: make global_dirty_tracking a bitmask huangy81
2021-06-29 16:01 ` [PATCH v12 3/6] migration/dirtyrate: introduce struct and adjust DirtyRateStat huangy81
2021-06-29 16:01 ` [PATCH v12 4/6] migration/dirtyrate: adjust order of registering thread huangy81
2021-06-29 16:01 ` [PATCH v12 5/6] migration/dirtyrate: move init step of calculation to main thread huangy81
2021-06-29 16:01 ` [PATCH v12 6/6] migration/dirtyrate: implement dirty-ring dirtyrate calculation huangy81
2021-08-29 23:11 ` [PATCH v12 0/6] support dirtyrate at the granualrity of vcpu Hyman
2021-09-20 15:45 ` Hyman
2021-09-20 16:00 ` Peter Xu
2021-10-15 1:32 ` Peter Xu
2021-10-15 2:07 ` Hyman Huang [this message]
2021-10-27 6:31 ` Zheng Chuan
2021-10-28 4:26 ` Hyman 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=78929c64-ca4d-6c6a-f371-99cd508e958a@chinatelecom.cn \
--to=huangy81@chinatelecom.cn \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhengchuan@huawei.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.