From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49000) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URemJ-00007y-Mf for qemu-devel@nongnu.org; Mon, 15 Apr 2013 04:28:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URemE-0001uI-Gq for qemu-devel@nongnu.org; Mon, 15 Apr 2013 04:28:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:15500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URemE-0001u9-8i for qemu-devel@nongnu.org; Mon, 15 Apr 2013 04:28:38 -0400 Message-ID: <516BB9C3.40508@redhat.com> Date: Mon, 15 Apr 2013 10:26:43 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20130411191533.GA25515@redhat.com> <51671DFF.80904@linux.vnet.ibm.com> <20130412104802.GA23467@redhat.com> <5167E797.2050103@redhat.com> <20130412112553.GB23467@redhat.com> <51681DAA.3000503@redhat.com> <20130414115911.GA4923@redhat.com> <516ABCCC.207@linux.vnet.ibm.com> <20130414160327.GB7165@redhat.com> <516ADBEA.5090100@linux.vnet.ibm.com> <20130414183041.GC7165@redhat.com> <516AFE23.104@linux.vnet.ibm.com> In-Reply-To: <516AFE23.104@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH RDMA support v5: 03/12] comprehensive protocol documentation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael R. Hines" Cc: aliguori@us.ibm.com, "Michael S. Tsirkin" , qemu-devel@nongnu.org, owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com Il 14/04/2013 21:06, Michael R. Hines ha scritto: > >> 3. Migration with RDMA support is experimental and unsupported. >> In particular, please do not expect it to work across qemu versions, >> and do not expect the management interface to be stable. >> > > The only correct statement here is that it's experimental. Actually no, this is correct. The capabilities are experimental too, the "x-rdma" will become "rdma" in the future, and we are free to modify the protocol. Will it happen? Perhaps not. But for the moment, that is the situation. The alternative is not merging, and it is a much worse alternative IMHO. Paolo