From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57638) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCsgm-0002O0-To for qemu-devel@nongnu.org; Tue, 05 Mar 2013 09:17:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCsgl-0007jh-Ux for qemu-devel@nongnu.org; Tue, 05 Mar 2013 09:17:56 -0500 Received: from nodalink.pck.nerim.net ([62.212.105.220]:54683 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCsgl-0007jQ-FB for qemu-devel@nongnu.org; Tue, 05 Mar 2013 09:17:55 -0500 Received: from irqsave.net (unknown [192.168.77.1]) by paradis.irqsave.net (Postfix) with ESMTP id 77B2A8741C4 for ; Tue, 5 Mar 2013 15:17:50 +0100 (CET) Date: Tue, 5 Mar 2013 15:18:46 +0100 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20130305141845.GA3411@irqsave.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Dataplane and vhost-blk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hello, I am looking for a way to help improving qemu block performance. APIC-V is a work in progress and the two options with public code are vho= st-* and virtio-blk-dataplane. The way of doing seems very similar (bypassing the qemu lock) and dedicat= ing a thread to each emulated virtio block device. vhost-* is in kernel while dataplane is in qemu. Performance seems similar. Dataplane seems to be a demonstrator to be replaced by an evolution of th= e qemu block layer made thread friendly and vhost-blk is not upstream yet. This left me with the following questions : Are dataplane and vhost-block purpose the same (speed) despite being push= ed by the same company (Red Hat) ? What is the best path I can take to help improve qemu block performance ? Best regards Beno=EEt