All of lore.kernel.org
 help / color / mirror / Atom feed
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, 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: Fri, 25 Oct 2013 11:00:39 -0400	[thread overview]
Message-ID: <526A8797.3040901@linux.vnet.ibm.com> (raw)
In-Reply-To: <5266DE16.8060508@redhat.com>

On 10/22/2013 04:20 PM, Eric Blake wrote:
> 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?
>

Oops =)

>> +++ 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.
>

Ah, yes. =)

      parent reply	other threads:[~2013-10-25 15:01 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
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 [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=526A8797.3040901@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=abali@us.ibm.com \
    --cc=aliguori@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 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.