From: Wei Yang <richardw.yang@linux.intel.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [Patch v2 0/6] migration/postcopy: enable compress during postcopy
Date: Mon, 16 Dec 2019 10:35:02 +0800 [thread overview]
Message-ID: <20191216023502.GA21865@richard> (raw)
In-Reply-To: <20191107123907.29791-1-richardw.yang@linux.intel.com>
Would this one be picked up in this version?
On Thu, Nov 07, 2019 at 08:39:01PM +0800, Wei Yang wrote:
>This patch set tries enable compress during postcopy.
>
>postcopy requires to place a whole host page, while migration thread migrate
>memory in target page size. This makes postcopy need to collect all target
>pages in one host page before placing via userfaultfd.
>
>To enable compress during postcopy, there are two problems to solve:
>
> 1. Random order for target page arrival
> 2. Target pages in one host page arrives without interrupt by target
> page from other host page
>
>The first one is handled by counting the number of target pages arrived
>instead of the last target page arrived.
>
>The second one is handled by:
>
> 1. Flush compress thread for each host page
> 2. Wait for decompress thread for before placing host page
>
>With the combination of these two changes, compress is enabled during
>postcopy.
>
>---
>v2:
> * use uintptr_t to calculate place_dest
> * check target pages belongs to the same host page
>
>Wei Yang (6):
> migration/postcopy: reduce memset when it is zero page and
> matches_target_page_size
> migration/postcopy: wait for decompress thread in precopy
> migration/postcopy: count target page number to decide the
> place_needed
> migration/postcopy: set all_zero to true on the first target page
> migration/postcopy: enable random order target page arrival
> migration/postcopy: enable compress during postcopy
>
> migration/migration.c | 11 -------
> migration/ram.c | 67 +++++++++++++++++++++++++++++++++----------
> 2 files changed, 52 insertions(+), 26 deletions(-)
>
>--
>2.17.1
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-12-16 2:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:39 [Patch v2 0/6] migration/postcopy: enable compress during postcopy Wei Yang
2019-11-07 12:39 ` [Patch v2 1/6] migration/postcopy: reduce memset when it is zero page and matches_target_page_size Wei Yang
2020-01-09 9:39 ` Juan Quintela
2019-11-07 12:39 ` [Patch v2 2/6] migration/postcopy: wait for decompress thread in precopy Wei Yang
2020-01-09 9:40 ` Juan Quintela
2019-11-07 12:39 ` [Patch v2 3/6] migration/postcopy: count target page number to decide the place_needed Wei Yang
2020-01-09 9:41 ` Juan Quintela
2019-11-07 12:39 ` [Patch v2 4/6] migration/postcopy: set all_zero to true on the first target page Wei Yang
2020-01-09 9:41 ` Juan Quintela
2019-11-07 12:39 ` [Patch v2 5/6] migration/postcopy: enable random order target page arrival Wei Yang
2019-11-07 14:30 ` Dr. David Alan Gilbert
2019-11-08 0:40 ` Wei Yang
2020-01-09 9:42 ` Juan Quintela
2019-11-07 12:39 ` [Patch v2 6/6] migration/postcopy: enable compress during postcopy Wei Yang
2020-01-09 9:44 ` Juan Quintela
2019-12-16 2:35 ` Wei Yang [this message]
2019-12-18 19:55 ` [Patch v2 0/6] " Dr. David Alan Gilbert
2020-01-06 1:29 ` Wei Yang
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=20191216023502.GA21865@richard \
--to=richardw.yang@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).