From: Wei Yang <richardw.yang@linux.intel.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Wei Yang <richardw.yang@linux.intel.com>,
quintela@redhat.com
Subject: Re: [Patch v2 0/6] migration/postcopy: enable compress during postcopy
Date: Mon, 6 Jan 2020 09:29:05 +0800 [thread overview]
Message-ID: <20200106012905.GB15834@richard> (raw)
In-Reply-To: <20191218195538.GW3707@work-vm>
On Wed, Dec 18, 2019 at 07:55:38PM +0000, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.yang@linux.intel.com) wrote:
>> Would this one be picked up in this version?
>
>I think that one is on Juan's list for the pull he's going to do soon.
>
>Dave
>
Happy New Year to all~
May I ask the plan for this patch set?
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2020-01-06 1:29 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 ` [Patch v2 0/6] " Wei Yang
2019-12-18 19:55 ` Dr. David Alan Gilbert
2020-01-06 1:29 ` Wei Yang [this message]
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=20200106012905.GB15834@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.