From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=39302 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OG9sm-00011H-8w for qemu-devel@nongnu.org; Sun, 23 May 2010 08:02:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OG9sd-00027p-Po for qemu-devel@nongnu.org; Sun, 23 May 2010 08:02:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42919) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OG9sd-00027j-Fm for qemu-devel@nongnu.org; Sun, 23 May 2010 08:02:07 -0400 Message-ID: <4BF91937.2070801@redhat.com> Date: Sun, 23 May 2010 15:01:59 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC PATCH 1/1] ceph/rbd block driver for qemu-kvm References: <20100519192222.GD61706@ncolin.muc.de> <4BF5A9D2.5080609@codemonkey.ws> In-Reply-To: <4BF5A9D2.5080609@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Blue Swirl , ceph-devel@vger.kernel.org, Christian Brunner , kvm@vger.kernel.org, qemu-devel@nongnu.org On 05/21/2010 12:29 AM, Anthony Liguori wrote: > > I'd be more interested in enabling people to build these types of > storage systems without touching qemu. > > Both sheepdog and ceph ultimately transmit I/O over a socket to a > central daemon, right? That incurs an extra copy. > So could we not standardize a protocol for this that both sheepdog and > ceph could implement? The protocol already exists, nbd. It doesn't support snapshotting etc. but we could extend it. But IMO what's needed is a plugin API for the block layer. -- error compiling committee.c: too many arguments to function