From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Keqian Zhu <zhukeqian1@huawei.com>
Cc: zhang.zhanghailiang@huawei.com,
Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Chao Fan <fanc.fnst@cn.fujitsu.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
jianjay.zhou@huawei.com, wanghaibin.wang@huawei.com
Subject: Re: [PATCH v2] migration: Count new_dirty instead of real_dirty
Date: Tue, 16 Jun 2020 10:35:51 +0100 [thread overview]
Message-ID: <20200616093551.GA2790@work-vm> (raw)
In-Reply-To: <20200616021059.25984-1-zhukeqian1@huawei.com>
* Keqian Zhu (zhukeqian1@huawei.com) wrote:
> real_dirty_pages becomes equal to total ram size after dirty log sync
> in ram_init_bitmaps, the reason is that the bitmap of ramblock is
> initialized to be all set, so old path counts them as "real dirty" at
> beginning.
>
> This causes wrong dirty rate and false positive throttling at the end
> of first ram save iteration.
>
> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
Since this function already returns num_dirty, why not just change the
caller to increment a counter based off the return value?
Can you point to the code which is using this value that triggers the
throttle?
Dave
> ---
> Changelog:
>
> v2:
> - use new_dirty_pages instead of accu_dirty_pages.
> - adjust commit messages.
>
> ---
> include/exec/ram_addr.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/exec/ram_addr.h b/include/exec/ram_addr.h
> index 7b5c24e928..a95e2e7c25 100644
> --- a/include/exec/ram_addr.h
> +++ b/include/exec/ram_addr.h
> @@ -443,7 +443,7 @@ static inline
> uint64_t cpu_physical_memory_sync_dirty_bitmap(RAMBlock *rb,
> ram_addr_t start,
> ram_addr_t length,
> - uint64_t *real_dirty_pages)
> + uint64_t *new_dirty_pages)
> {
> ram_addr_t addr;
> unsigned long word = BIT_WORD((start + rb->offset) >> TARGET_PAGE_BITS);
> @@ -469,7 +469,6 @@ uint64_t cpu_physical_memory_sync_dirty_bitmap(RAMBlock *rb,
> if (src[idx][offset]) {
> unsigned long bits = atomic_xchg(&src[idx][offset], 0);
> unsigned long new_dirty;
> - *real_dirty_pages += ctpopl(bits);
> new_dirty = ~dest[k];
> dest[k] |= bits;
> new_dirty &= bits;
> @@ -502,7 +501,6 @@ uint64_t cpu_physical_memory_sync_dirty_bitmap(RAMBlock *rb,
> start + addr + offset,
> TARGET_PAGE_SIZE,
> DIRTY_MEMORY_MIGRATION)) {
> - *real_dirty_pages += 1;
> long k = (start + addr) >> TARGET_PAGE_BITS;
> if (!test_and_set_bit(k, dest)) {
> num_dirty++;
> @@ -511,6 +509,7 @@ uint64_t cpu_physical_memory_sync_dirty_bitmap(RAMBlock *rb,
> }
> }
>
> + *new_dirty_pages += num_dirty;
> return num_dirty;
> }
> #endif
> --
> 2.19.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-06-16 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 2:10 [PATCH v2] migration: Count new_dirty instead of real_dirty Keqian Zhu
2020-06-16 9:35 ` Dr. David Alan Gilbert [this message]
2020-06-16 9:48 ` zhukeqian
2020-06-16 9:58 ` Dr. David Alan Gilbert
2020-06-16 11:20 ` zhukeqian
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=20200616093551.GA2790@work-vm \
--to=dgilbert@redhat.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=jianjay.zhou@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wanghaibin.wang@huawei.com \
--cc=zhang.zhanghailiang@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).