From: Kunkun Jiang <jiangkunkun@huawei.com>
To: David Edmondson <dme@dme.org>,
Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: Zenghui Yu <yuzenghui@huawei.com>,
wanghaibin.wang@huawei.com, Keqian Zhu <zhukeqian1@huawei.com>
Subject: Re: [PATCH v2 3/3] migration/ram: Optimize ram_save_host_page()
Date: Wed, 3 Mar 2021 19:47:20 +0800 [thread overview]
Message-ID: <1e7cda11-7189-491b-9d2c-bfc1926f2b69@huawei.com> (raw)
In-Reply-To: <m2k0qoliok.fsf@dme.org>
On 2021/3/3 16:56, David Edmondson wrote:
> On Monday, 2021-03-01 at 16:21:32 +08, Kunkun Jiang wrote:
>
>> Starting from pss->page, ram_save_host_page() will check every page
>> and send the dirty pages up to the end of the current host page or
>> the boundary of used_length of the block. If the host page size is
>> a huge page, the step "check" will take a lot of time.
>>
>> This will improve performance to use migration_bitmap_find_dirty().
> This is cleaner, thank you.
>
> I was hoping to just invert the body of the loop - something like
> (completely untested):
Sorry for my misunderstanding.
I will improve it in the next version.
> do {
> int pages_this_iteration = 0;
>
> /* Check if the page is dirty and, if so, send it. */
> if (migration_bitmap_clear_dirty(rs, pss->block, pss->page)) {
> pages_this_iteration = ram_save_target_page(rs, pss, last_stage);
> if (pages_this_iteration < 0) {
> return pages_this_iteration;
> }
>
> pages += pages_this_iteration;
>
> /*
> * Allow rate limiting to happen in the middle of huge pages if
> * the current iteration sent something.
> */
> if (pagesize_bits > 1 && pages_this_iteration > 0) {
> migration_rate_limit();
> }
I missed the case that the value of pages_this_iteration is 0. 😅
> }
> pss->page = migration_bitmap_find_dirty(rs, pss->block, pss->page);
> } while ((pss->page < hostpage_boundary) &&
> offset_in_ramblock(pss->block,
> ((ram_addr_t)pss->page) << TARGET_PAGE_BITS));
> /* The offset we leave with is the min boundary of host page and block */
> pss->page = MIN(pss->page, hostpage_boundary) - 1;
Best Regards.
Kunkun Jiang
>> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
>> Signed-off-by: Kunkun Jiang <jiangkunkun@huawei.com>
>> ---
>> migration/ram.c | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/migration/ram.c b/migration/ram.c
>> index 3a9115b6dc..a1374db356 100644
>> --- a/migration/ram.c
>> +++ b/migration/ram.c
>> @@ -1991,6 +1991,8 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
>> int tmppages, pages = 0;
>> size_t pagesize_bits =
>> qemu_ram_pagesize(pss->block) >> TARGET_PAGE_BITS;
>> + unsigned long hostpage_boundary =
>> + QEMU_ALIGN_UP(pss->page + 1, pagesize_bits);
>> unsigned long start_page = pss->page;
>> int res;
>>
>> @@ -2002,7 +2004,7 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
>> do {
>> /* Check the pages is dirty and if it is send it */
>> if (!migration_bitmap_clear_dirty(rs, pss->block, pss->page)) {
>> - pss->page++;
>> + pss->page = migration_bitmap_find_dirty(rs, pss->block, pss->page);
>> continue;
>> }
>>
>> @@ -2012,16 +2014,16 @@ static int ram_save_host_page(RAMState *rs, PageSearchStatus *pss,
>> }
>>
>> pages += tmppages;
>> - pss->page++;
>> + pss->page = migration_bitmap_find_dirty(rs, pss->block, pss->page);
>> /* Allow rate limiting to happen in the middle of huge pages */
>> if (pagesize_bits > 1) {
>> migration_rate_limit();
>> }
>> - } while ((pss->page & (pagesize_bits - 1)) &&
>> + } while ((pss->page < hostpage_boundary) &&
>> offset_in_ramblock(pss->block,
>> ((ram_addr_t)pss->page) << TARGET_PAGE_BITS));
>> - /* The offset we leave with is the last one we looked at */
>> - pss->page--;
>> + /* The offset we leave with is the min boundary of host page and block */
>> + pss->page = MIN(pss->page, hostpage_boundary) - 1;
>>
>> res = ram_save_release_protection(rs, pss, start_page);
>> return (res < 0 ? res : pages);
>> --
>> 2.23.0
> dme.
next prev parent reply other threads:[~2021-03-03 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:21 [PATCH v2 0/3] Some modifications about ram_save_host_page() Kunkun Jiang
2021-03-01 8:21 ` [PATCH v2 1/3] migration/ram: Modify the code comment of ram_save_host_page() Kunkun Jiang
2021-03-03 8:38 ` David Edmondson
2021-03-01 8:21 ` [PATCH v2 2/3] migration/ram: Modify ram_save_host_page() to match the comment Kunkun Jiang
2021-03-03 8:37 ` david.edmondson
2021-03-01 8:21 ` [PATCH v2 3/3] migration/ram: Optimize ram_save_host_page() Kunkun Jiang
2021-03-03 8:56 ` David Edmondson
2021-03-03 11:47 ` Kunkun Jiang [this message]
2021-03-03 14:55 ` David Edmondson
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=1e7cda11-7189-491b-9d2c-bfc1926f2b69@huawei.com \
--to=jiangkunkun@huawei.com \
--cc=dgilbert@redhat.com \
--cc=dme@dme.org \
--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).