From: Eric Blake <eblake@redhat.com>
To: mrhines@linux.vnet.ibm.com, qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, quintela@redhat.com, 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] rdma: rename 'x-rdma' => 'rdma'
Date: Tue, 22 Oct 2013 21:20:38 +0100 [thread overview]
Message-ID: <5266DE16.8060508@redhat.com> (raw)
In-Reply-To: <1382461164-8854-1-git-send-email-mrhines@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
On 10/22/2013 05:59 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,
> there as been very good participation in testing and running.
>
> 1. Parallel RDMA migrations are working
> 2. IPv6 migration is working
> 3. Libvirt patches are ready
> 4. virt-test is working
>
> Any objections to removing the experimental tag?
>
> There is one remaining bug: qemu-system-i386 does not compile
> with RDMA: I have very zero access to 32-bit hardware
> using RDMA, so this hasn't been much of a priority. It seems
> safer to *not* submit non-testable patch rather than submit
> submit a fix just for the sake of compiling =)
>
> Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
> ---
>
> TODO:
> =====
> -1. 'migrate x-rdma:host:port' and '-incoming x-rdma' options will be
> +1. 'migrate rdma:host:port' and '-incoming rdma' options will be
> renamed to 'rdma' after the experimental phase of this work has
> completed upstream.
Shouldn't you remove step 1 and renumber the rest of the list
altogether, rather than just altering the comment to make it out-of-date?
> +++ 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)
I'd also recommend tweaking this to say 'since 1.7', since the spelling
'rdma-pin-all' is new to this release.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-10-22 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 16:59 [Qemu-devel] [PATCH] rdma: rename 'x-rdma' => 'rdma' mrhines
2013-10-22 20:20 ` Eric Blake [this message]
2013-10-23 6:25 ` Paolo Bonzini
2013-10-25 15:03 ` Michael R. Hines
2013-10-25 15:14 ` Paolo Bonzini
2013-10-26 8:45 ` Michael R. Hines
2013-10-26 17:13 ` Paolo Bonzini
2013-10-25 15:00 ` 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=5266DE16.8060508@redhat.com \
--to=eblake@redhat.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=chegu_vinod@hp.com \
--cc=gokul@us.ibm.com \
--cc=mrhines@linux.vnet.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).