From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: quintela@redhat.com, abali@us.ibm.com, qemu-devel@nongnu.org,
owasserm@redhat.com, onom@us.ibm.com, hinesmr@cn.ibm.com,
"Michael R. Hines" <mrhines@us.ibm.com>,
gokul@us.ibm.com, pbonzini@redhat.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] [PATCH v4 resend] rdma: rename 'x-rdma' => 'rdma'
Date: Thu, 19 Dec 2013 04:52:51 +0800 [thread overview]
Message-ID: <52B20B23.3060409@linux.vnet.ibm.com> (raw)
In-Reply-To: <52B1A86E.9040608@redhat.com>
On 12/18/2013 09:51 PM, Eric Blake wrote:
> On 12/17/2013 10:43 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 migrations are working
>> 2. IPv6 migration is working
>> 3. virt-test is working
>>
>> +++ b/qapi-schema.json
>> @@ -671,10 +671,9 @@
>> # 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)
>> +# Disabled by default. (since 1.7)
> Alas, we missed 1.7. This should now read 'since 2.0'.
>
Thanks, Eric.
- Michael
prev parent reply other threads:[~2013-12-18 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 5:43 [Qemu-devel] [PATCH v4 resend] rdma: rename 'x-rdma' => 'rdma' mrhines
2013-12-18 13:51 ` Eric Blake
2013-12-18 20:52 ` 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=52B20B23.3060409@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=hinesmr@cn.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 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.