From: Kunkun Jiang <jiangkunkun@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Juan Quintela" <quintela@redhat.com>,
"David Edmondson" <dme@dme.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"Peter Xu" <peterx@redhat.com>, "Cédric Le Goater" <clg@kaod.org>,
"Alexey Romko" <nevilad@yahoo.com>,
"Zenghui Yu" <yuzenghui@huawei.com>,
wanghaibin.wang@huawei.com, "Keqian Zhu" <zhukeqian1@huawei.com>,
"Andrey Gruzdev" <andrey.gruzdev@virtuozzo.com>
Subject: Re: [PATCH v4 0/2] Some modification about ram_save_host_page()
Date: Wed, 7 Apr 2021 17:32:31 +0800 [thread overview]
Message-ID: <04961810-a0d0-4bf4-27bd-fc2f3b208a6c@huawei.com> (raw)
In-Reply-To: <YGyXEhvSxW32uywG@work-vm>
Hi Dave,
On 2021/4/7 1:14, Dr. David Alan Gilbert wrote:
> * Kunkun Jiang (jiangkunkun@huawei.com) wrote:
>> Kindly ping,
>>
>> Hi David Alan Gilbert,
>> Will this series be picked up soon, or is there any other work for me to do?
> You don't need to do anything, but it did miss the cutoff for soft
> freeze; since it's an optimisation not a fix; it's still on my list so
> it'll go in just as soon as 6.1 opens up.
>
> Dave
Okay, I see. Thank you.
Best Regards,
Kunkun Jiang
>> Best Regards,
>> Kunkun Jiang
>>
>> On 2021/3/16 20:57, Kunkun Jiang wrote:
>>> Hi all,
>>>
>>> This series include patches as below:
>>> Patch 1:
>>> - reduce unnecessary rate limiting in ram_save_host_page()
>>>
>>> Patch 2:
>>> - optimized ram_save_host_page() by using migration_bitmap_find_dirty() to find
>>> dirty pages
>>>
>>> History:
>>>
>>> v3 -> v4:
>>> - Remove the modification to ram_save_host_page() comment [Peter Xu]
>>> - Remove the renaming of tmppages
>>>
>>> v2 -> v3:
>>> - Reduce unnecessary rate limiting if nothing is sent in the current iteration [David Edmondson]
>>> - Invert the body of the loop in ram_save_host_page() [David Edmondson]
>>>
>>> v1 -> v2:
>>> - Modify ram_save_host_page() comment [David Edmondson]
>>> - Remove 'goto' [David Edmondson]
>>>
>>> Kunkun Jiang (2):
>>> migration/ram: Reduce unnecessary rate limiting
>>> migration/ram: Optimize ram_save_host_page()
>>>
>>> migration/ram.c | 34 +++++++++++++++++++---------------
>>> 1 file changed, 19 insertions(+), 15 deletions(-)
>>>
next prev parent reply other threads:[~2021-04-07 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 12:57 [PATCH v4 0/2] Some modification about ram_save_host_page() Kunkun Jiang
2021-03-16 12:57 ` [PATCH v4 1/2] migration/ram: Reduce unnecessary rate limiting Kunkun Jiang
2021-03-16 21:39 ` Peter Xu
2021-03-17 1:37 ` Kunkun Jiang
2021-03-17 10:43 ` David Edmondson
2021-03-17 12:05 ` Dr. David Alan Gilbert
2021-03-16 12:57 ` [PATCH v4 2/2] migration/ram: Optimize ram_save_host_page() Kunkun Jiang
2021-03-16 21:39 ` Peter Xu
2021-04-06 13:19 ` [PATCH v4 0/2] Some modification about ram_save_host_page() Kunkun Jiang
2021-04-06 17:14 ` Dr. David Alan Gilbert
2021-04-07 9:32 ` Kunkun Jiang [this message]
2021-05-11 9:17 ` Dr. David Alan Gilbert
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=04961810-a0d0-4bf4-27bd-fc2f3b208a6c@huawei.com \
--to=jiangkunkun@huawei.com \
--cc=andrey.gruzdev@virtuozzo.com \
--cc=clg@kaod.org \
--cc=dgilbert@redhat.com \
--cc=dme@dme.org \
--cc=nevilad@yahoo.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.com \
--cc=zhukeqian1@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 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).