From: Lai Jiangshan <jiangshanlai@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] add migration capability to bypass the shared memory
Date: Wed, 10 Aug 2016 09:09:45 +0800 [thread overview]
Message-ID: <CAJhGHyDVC95msnLXRzpnZxO=0roaQH_xUUv225D+0E+XGNaj1A@mail.gmail.com> (raw)
In-Reply-To: <20160809191216.GF2025@work-vm>
On Wed, Aug 10, 2016 at 3:12 AM, Dr. David Alan Gilbert
<dgilbert@redhat.com> wrote:
> * Lai Jiangshan (jiangshanlai@gmail.com) wrote:
>> The feature vm-template makes the containers(VMs) can
>> be started in 130ms and save 80M memory for every
>> container(VM). So that the hyper containers are fast
>> and high-density as normal containers.
>
> Very nice.
Hello, David,
thank you for your review.
>>
>> 4) yet-another-post-copy-migration
>> It is a possible feature, no toolkit can do it well now.
>> Using nbd server/client on the memory file is reluctantly Ok but
>> inconvenient. A special feature for tmpfs might be needed to
>> fully complete this feature.
>> No one need yet another post copy migration method,
>> but it is possible when some crazy man need it.
>
> Well as the crazy man who wrote the current postcopy code, what would
> you need it to do that the current one can't?
I don't think we need to add a new post-copy-migration method.
I mentioned it for showing one of the potentials of this patch.
>
> I can't see anything noticeably wrong with your code; but I see the bot
> gave you some style warnings.
Fixed in v2.
Thanks,
Lai
>
> Dave
>
>> Signed-off-by: Lai Jiangshan <jiangshanlai@gmail.com>
>> ---
>> exec.c | 5 +++++
>> include/exec/cpu-common.h | 1 +
>> include/migration/migration.h | 1 +
>> migration/migration.c | 9 +++++++++
>> migration/ram.c | 37 ++++++++++++++++++++++++++++---------
>> qapi-schema.json | 6 +++++-
>> qmp-commands.hx | 3 +++
>> 7 files changed, 52 insertions(+), 10 deletions(-)
next prev parent reply other threads:[~2016-08-10 1:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:10 [Qemu-devel] [PATCH] add migration capability to bypass the shared memory Lai Jiangshan
2016-08-09 13:51 ` no-reply
2016-08-09 19:12 ` Dr. David Alan Gilbert
2016-08-10 0:54 ` [Qemu-devel] [PATCH V2] " Lai Jiangshan
2016-08-10 1:22 ` Fam Zheng
2016-08-10 2:22 ` Li, Liang Z
2016-08-10 3:22 ` Lai Jiangshan
2016-08-10 5:04 ` Li, Liang Z
2016-08-10 9:11 ` Juan Quintela
2016-08-11 7:11 ` Li, Liang Z
2016-08-11 14:31 ` Lai Jiangshan
2016-08-11 14:45 ` Lai Jiangshan
2017-09-21 3:41 ` Zhang Haoyu
2016-08-12 6:48 ` Li, Liang Z
2016-08-12 7:19 ` Lai Jiangshan
2017-09-25 7:42 ` Zhang Haoyu
2017-09-25 12:13 ` Zhang Haoyu
2016-08-10 1:09 ` Lai Jiangshan [this message]
2016-08-10 9:03 ` [Qemu-devel] [PATCH] " Juan Quintela
2016-08-30 4:11 ` Lai Jiangshan
2016-11-18 13:01 ` Alexander Graf
2017-01-12 19:19 ` Jianjun Duan
2017-01-13 4:44 ` Lai Jiangshan
2017-01-16 17:38 ` Jianjun Duan
2017-09-21 6:33 ` Zhang Haoyu
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='CAJhGHyDVC95msnLXRzpnZxO=0roaQH_xUUv225D+0E+XGNaj1A@mail.gmail.com' \
--to=jiangshanlai@gmail.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).