From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.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
Subject: Re: [Qemu-devel] [PATCH v5 10/12] rdma: introduce capability x-rdma-pin-all
Date: Mon, 22 Apr 2013 16:59:38 -0400 [thread overview]
Message-ID: <5175A4BA.3060706@linux.vnet.ibm.com> (raw)
In-Reply-To: <51759C91.9030008@redhat.com>
On 04/22/2013 04:24 PM, Eric Blake wrote:
> On 04/21/2013 03:17 PM, mrhines@linux.vnet.ibm.com wrote:
>> From: "Michael R. Hines" <mrhines@us.ibm.com>
>>
>> This capability allows you to disable dynamic chunk registration
>> for better throughput on high-performance links.
>>
>> For example, using an 8GB RAM virtual machine with all 8GB of memory in
>> active use and the VM itself is completely idle using a 40 gbps infiniband link:
>>
>> 1. x-pin-all disabled total time: approximately 7.5 seconds @ 9.5 Gbps
>> 2. x-pin-all enabled total time: approximately 4 seconds @ 26 Gbps
> Naming here doesn't match the actual bit name; but it is obvious enough
> to know what you meant.
>
> Thanks for doing this, by the way - the default-to-disabled is a bit
> nicer to manage from libvirt's perspective.
>
>> 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.
>>
>> Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
>> ---
>> include/migration/migration.h | 2 ++
>> migration.c | 9 +++++++++
>> qapi-schema.json | 7 ++++++-
>> 3 files changed, 17 insertions(+), 1 deletion(-)
>
>> +++ b/qapi-schema.json
>> @@ -602,10 +602,15 @@
>> # This feature allows us to minimize migration traffic for certain work
>> # loads, by sending compressed difference of the pages
>> #
>> +# @x-rdma-pin-all: (since 1.5) Controls whether or not the entire VM memory footprint is
> Trailing whitespace, and line longer than 80 columns. You ought to
> rewrap this, and make sure it passes checkpatch.pl.
>
> But since that is whitespace-only, feel free to add:
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
Acknowledged.
next prev parent reply other threads:[~2013-04-22 21:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 21:17 [Qemu-devel] [PATCH v5 00/12] rdma: migration support mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 01/12] rdma: add documentation mrhines
2013-04-22 20:16 ` Eric Blake
2013-04-22 20:58 ` Michael R. Hines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 02/12] rdma: export yield_until_fd_readable() mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 03/12] rdma: export throughput w/ MigrationStats QMP mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 04/12] rdma: introduce qemu_get_max_size() mrhines
2013-04-22 20:20 ` Eric Blake
2013-04-22 20:59 ` Michael R. Hines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 05/12] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 06/12] rdma: export qemu_fflush() mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 07/12] rdma: introduce ram_handle_compressed() mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 08/12] rdma: introduce qemu_ram_foreach_block() mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 09/12] rdma: new QEMUFileOps hooks mrhines
2013-04-21 21:17 ` [Qemu-devel] [PATCH v5 10/12] rdma: introduce capability x-rdma-pin-all mrhines
2013-04-22 20:24 ` Eric Blake
2013-04-22 20:59 ` Michael R. Hines [this message]
2013-04-21 21:18 ` [Qemu-devel] [PATCH v5 11/12] rdma: core logic mrhines
2013-04-21 21:18 ` [Qemu-devel] [PATCH v5 12/12] rdma: send pc.ram mrhines
-- strict thread matches above, loose matches on Subject: below --
2013-04-23 1:55 [Qemu-devel] [PATCH v5 00/12] rdma: migration support mrhines
2013-04-23 1:55 ` [Qemu-devel] [PATCH v5 10/12] rdma: introduce capability x-rdma-pin-all mrhines
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=5175A4BA.3060706@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=gokul@us.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).