From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYrtS-0005H3-O1 for qemu-devel@nongnu.org; Wed, 23 Oct 2013 02:26:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYrtK-00041e-Av for qemu-devel@nongnu.org; Wed, 23 Oct 2013 02:26:10 -0400 Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:45195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYrtK-00041a-3u for qemu-devel@nongnu.org; Wed, 23 Oct 2013 02:26:02 -0400 Received: by mail-we0-f180.google.com with SMTP id q59so305925wes.39 for ; Tue, 22 Oct 2013 23:26:01 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <52676BF6.7010305@redhat.com> Date: Wed, 23 Oct 2013 07:25:58 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1382461164-8854-1-git-send-email-mrhines@linux.vnet.ibm.com> <5266DE16.8060508@redhat.com> In-Reply-To: <5266DE16.8060508@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] rdma: rename 'x-rdma' => 'rdma' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: aliguori@us.ibm.com, quintela@redhat.com, qemu-devel@nongnu.org, mrhines@linux.vnet.ibm.com, owasserm@redhat.com, onom@us.ibm.com, abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com, chegu_vinod@hp.com Il 22/10/2013 21:20, Eric Blake ha scritto: >> > -# @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. I would also leave this as experimental for now. Basically the point of the "experimental" designation was to ensure that RDMA protocol changes might not preserve backwards compatibility. The capability is a separate thing from the protocol, as it would likely apply to any migration-over-RDMA implementation Paolo