From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, owasserm@redhat.com,
onom@us.ibm.com, abali@us.ibm.com, mrhines@us.ibm.com,
gokul@us.ibm.com, pbonzini@redhat.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] [PATCH v2] rdma: rename 'x-rdma' => 'rdma'
Date: Wed, 06 Nov 2013 13:54:57 -0500 [thread overview]
Message-ID: <527A9081.1000507@linux.vnet.ibm.com> (raw)
In-Reply-To: <52796F0C.8010107@redhat.com>
On 11/05/2013 05:19 PM, Eric Blake wrote:
> On 10/26/2013 02:03 PM, mrhines@linux.vnet.ibm.com wrote:
>> From: "Michael R. Hines" <mrhines@us.ibm.com>
>>
>> As far as we can tell, all known bugs have been fixed:
>>
>> 1. Parallel RDMA migrations are working
>> 2. IPv6 migration is working
>> 3. Libvirt patches are ready
>> 4. virt-test is working
>>
>> Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
>> ---
>> docs/rdma.txt | 24 ++++++++++--------------
>> migration-rdma.c | 2 +-
>> migration.c | 6 +++---
>> qapi-schema.json | 4 ++--
>> 4 files changed, 16 insertions(+), 20 deletions(-)
>> +++ b/qapi-schema.json
>> @@ -615,7 +615,7 @@
>> # This feature allows us to minimize migration traffic for certain work
>> # loads, by sending compressed difference of the pages
>> #
>> -# @x-rdma-pin-all: Controls whether or not the entire VM memory footprint is
>> +# @rdma-pin-all: Controls whether or not the entire VM memory footprint is
>> # mlock()'d on demand or all at once. Refer to docs/rdma.txt for usage.
>> # Disabled by default. Experimental: may (or may not) be renamed after
>> # further testing is complete. (since 1.6)
> This text is still out-of-date. s/1.6/1.7/ (if we are still trying to
> get it in 1.7), as well as removing mention of it being experimental.
>
Thanks, Erik. Very silly of me to miss that.
- Michael
prev parent reply other threads:[~2013-11-06 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 20:03 [Qemu-devel] [PATCH v2] rdma: rename 'x-rdma' => 'rdma' mrhines
2013-11-05 22:19 ` Eric Blake
2013-11-06 18:54 ` Michael R. Hines [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=527A9081.1000507@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=abali@us.ibm.com \
--cc=chegu_vinod@hp.com \
--cc=eblake@redhat.com \
--cc=gokul@us.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=onom@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).