From: David Hildenbrand <david@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>, Peter Xu <peterx@redhat.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"quintela@redhat.com" <quintela@redhat.com>
Subject: Re: [PATCH v3] migration: clear the memory region dirty bitmap when skipping free pages
Date: Fri, 23 Jul 2021 10:16:35 +0200 [thread overview]
Message-ID: <9d891b0f-65ff-b6e8-3ef1-81d038e9d010@redhat.com> (raw)
In-Reply-To: <30a4eb65544241719a55bc2a9e9e1605@intel.com>
On 23.07.21 10:14, Wang, Wei W wrote:
> On Friday, July 23, 2021 3:50 PM, David Hildenbrand wrote:
>>
>> Migration of a 8 GiB VM
>> * within the same host
>> * after Linux is up and idle
>> * free page hinting enabled
>> * after dirtying most VM memory using memhog
>
> Thanks for the tests!
>
> I think it would be better to test using idle guests (no memhog).
> With memhog eating most of the guest free pages, it's likely no or very few free pages are reported during the test.
*After dirtying*. memhog is no longer running.
... and also look again at the numbers how much memory we actually
migrate :)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-07-23 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 8:30 [PATCH v3] migration: clear the memory region dirty bitmap when skipping free pages Wei Wang
2021-07-22 9:47 ` David Hildenbrand
2021-07-22 9:57 ` Wang, Wei W
2021-07-22 14:51 ` Peter Xu
2021-07-22 14:51 ` David Hildenbrand
2021-07-22 17:41 ` Peter Xu
2021-07-23 7:50 ` David Hildenbrand
2021-07-23 8:14 ` Wang, Wei W
2021-07-23 8:16 ` David Hildenbrand [this message]
2021-07-23 8:32 ` Wang, Wei W
2021-07-23 12:51 ` Peter Xu
2021-07-23 12:52 ` David Hildenbrand
2021-07-23 8:03 ` David Hildenbrand
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=9d891b0f-65ff-b6e8-3ef1-81d038e9d010@redhat.com \
--to=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei.w.wang@intel.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).