From: Chegu Vinod <chegu_vinod@hp.com>
To: mrhines@linux.vnet.ibm.com
Cc: aliguori@us.ibm.com, quintela@redhat.com, qemu-devel@nongnu.org,
owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com,
gokul@us.ibm.com, pbonzini@redhat.com, knoel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v9 00/14] rdma: migration support
Date: Sat, 15 Jun 2013 15:51:45 -0700 [thread overview]
Message-ID: <51BCF001.7080204@hp.com> (raw)
In-Reply-To: <1371242153-11262-1-git-send-email-mrhines@linux.vnet.ibm.com>
On 6/14/2013 1:35 PM, mrhines@linux.vnet.ibm.com wrote:
> From: "Michael R. Hines" <mrhines@us.ibm.com>
>
> Changes since v8:
> For very large virtual machines, pinning can take a long time.
> While this does not affect the migration's *actual* time itself,
> it is still important for the user to know what's going on and
> to know what component of the total time is actual taken up by
> pinning.
>
> For example, using a 14GB virtual machine, pinning can take as
> long as 5 seconds, for which the user would not otherwise know
> what was happening.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Chegu Vinod <chegu_vinod@hp.com>
Tested-by: Chegu Vinod <chegu_vinod@hp.com>
Thx
Vinod
>
> Wiki: http://wiki.qemu.org/Features/RDMALiveMigration
> Github: git@github.com:hinesmr/qemu.git
>
> Here is a brief summary of total migration time and downtime using RDMA:
>
> Using a 40gbps infiniband link performing a worst-case stress test,
> using an 8GB RAM virtual machine:
> Using the following command:
>
> $ apt-get install stress
> $ stress --vm-bytes 7500M --vm 1 --vm-keep
>
> RESULTS:
>
> 1. Migration throughput: 26 gigabits/second.
> 2. Downtime (stop time) varies between 15 and 100 milliseconds.
>
> EFFECTS of memory registration on bulk phase round:
>
> For example, in the same 8GB RAM example with all 8GB of memory in
> active use and the VM itself is completely idle using the same 40 gbps
> infiniband link:
>
> 1. x-rdma-pin-all disabled total time: approximately 7.5 seconds @ 9.5 Gbps
> 2. x-rdma-pin-all enabled total time: approximately 4 seconds @ 26 Gbps
>
> These numbers would of course scale up to whatever size virtual machine
> you have to migrate using RDMA.
>
> Enabling this feature does *not* have any measurable affect on
> migration *downtime*. This is because, without this feature, all of the
> memory will have already been registered already in advance during
> the bulk round and does not need to be re-registered during the successive
> iteration rounds.
>
> The following changes since commit f3aa844bbb2922a5b8393d17620eca7d7e921ab3:
>
> build: include config-{, all-}devices.mak after defining CONFIG_SOFTMMU and CONFIG_USER_ONLY (2013-04-24 12:18:41 -0500)
>
> are available in the git repository at:
>
> git@github.com:hinesmr/qemu.git rdma_patch_v9
>
> for you to fetch changes up to 75e6fac1f642885b93cefe6e1874d648e9850f8f:
>
> rdma: send pc.ram (2013-04-24 14:55:01 -0400)
>
> ----------------------------------------------------------------
> Michael R. Hines (14):
> rdma: add documentation
> rdma: introduce qemu_update_position()
> rdma: export yield_until_fd_readable()
> rdma: export throughput w/ MigrationStats QMP
> rdma: introduce qemu_file_mode_is_not_valid()
> rdma: export qemu_fflush()
> rdma: introduce ram_handle_compressed()
> rdma: introduce qemu_ram_foreach_block()
> rdma: new QEMUFileOps hooks
> rdma: introduce capability x-rdma-pin-all
> rdma: core logic
> rdma: send pc.ram
> rdma: fix mlock() freezes and accounting
> rdma: add pin-all accounting timestamp to QMP statistics
>
> Makefile.objs | 1 +
> arch_init.c | 69 +-
> configure | 29 +
> docs/rdma.txt | 415 ++++++
> exec.c | 9 +
> hmp.c | 6 +
> include/block/coroutine.h | 6 +
> include/exec/cpu-common.h | 5 +
> include/migration/migration.h | 32 +
> include/migration/qemu-file.h | 32 +
> migration-rdma.c | 2831 +++++++++++++++++++++++++++++++++++++++++
> migration.c | 36 +-
> qapi-schema.json | 15 +-
> qemu-coroutine-io.c | 23 +
> savevm.c | 114 +-
> 15 files changed, 3574 insertions(+), 49 deletions(-)
> create mode 100644 docs/rdma.txt
> create mode 100644 migration-rdma.c
>
next prev parent reply other threads:[~2013-06-15 22:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 20:35 [Qemu-devel] [PATCH v9 00/14] rdma: migration support mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 01/14] rdma: add documentation mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 02/14] rdma: introduce qemu_update_position() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 03/14] rdma: export yield_until_fd_readable() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 04/14] rdma: export throughput w/ MigrationStats QMP mrhines
2013-06-15 9:09 ` Eric Blake
2013-06-16 4:04 ` Michael R. Hines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 05/14] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 06/14] rdma: export qemu_fflush() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 07/14] rdma: introduce ram_handle_compressed() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 08/14] rdma: introduce qemu_ram_foreach_block() mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 09/14] rdma: new QEMUFileOps hooks mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 10/14] rdma: introduce capability x-rdma-pin-all mrhines
2013-06-15 9:05 ` Eric Blake
2013-06-16 4:04 ` Michael R. Hines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 11/14] rdma: core logic mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 12/14] rdma: send pc.ram mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 13/14] rdma: fix mlock() freezes and accounting mrhines
2013-06-14 20:35 ` [Qemu-devel] [PATCH v9 14/14] rdma: add pin-all accounting timestamp to QMP statistics mrhines
2013-06-15 9:06 ` Eric Blake
2013-06-15 17:32 ` Paolo Bonzini
2013-06-16 4:06 ` Michael R. Hines
2013-06-16 4:05 ` Michael R. Hines
2013-06-16 18:37 ` Chegu Vinod
2013-06-18 20:17 ` Michael R. Hines
2013-06-15 22:51 ` Chegu Vinod [this message]
2013-06-16 4:07 ` [Qemu-devel] [PATCH v9 00/14] rdma: migration support Michael R. Hines
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=51BCF001.7080204@hp.com \
--to=chegu_vinod@hp.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=gokul@us.ibm.com \
--cc=knoel@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@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).