From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOkL1-0001cw-S6 for qemu-devel@nongnu.org; Tue, 02 Sep 2014 05:25:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOkKw-0007a0-Tl for qemu-devel@nongnu.org; Tue, 02 Sep 2014 05:25:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23861) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOkKw-0007Zm-L3 for qemu-devel@nongnu.org; Tue, 02 Sep 2014 05:25:14 -0400 Date: Tue, 2 Sep 2014 10:25:10 +0100 From: Stefan Hajnoczi Message-ID: <20140902092510.GC29067@stefanha-thinkpad.redhat.com> References: <20140829172218.GD16755@irqsave.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bKyqfOwhbdpXa4YI" Content-Disposition: inline In-Reply-To: <20140829172218.GD16755@irqsave.net> Subject: Re: [Qemu-devel] tcmu-runner and QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?iso-8859-1?Q?Beno=EEt?= Canet Cc: kwolf@redhat.com, pbonzini@redhat.com, agrover@redhat.com, qemu-devel@nongnu.org --bKyqfOwhbdpXa4YI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 29, 2014 at 07:22:18PM +0200, Beno=EEt Canet wrote: > Listening at Palo's suggestion I started discussing privately with > Andy about integrating LIO and the QEMU block layer together using > tcmu-runner: https://github.com/agrover/tcmu-runner. I looked at this briefly when Andy posted the userspace target patches to the target-devel list. The easiest approach is to write a tool similar to qemu-nbd that speaks the userspace target protocol (i.e. mmap the shared memory). If the tcmu setup code is involved, maybe providing a libtcmu with the setup code would be useful. I suspect that other projects may want to integrate userspace target support too. It's easier to let people add it to their codebase rather than hope they bring their codebase into tcmu-runner. The qemu-lio tool would live in the QEMU codebase and reuse all the infrastructure. For example, it could include a QMP monitor just like the one you are adding to qemu-nbd. Stefan --bKyqfOwhbdpXa4YI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUBYz2AAoJEJykq7OBq3PI72YIAIy8ThpEuXWZkOqUF6kC9tOp OLmh8uVzTBrSLZkgXGBySE7lTX3mEYqMzzc/06x54yXgcFMKkW0s31Phmxa7xr0A IUw7WR4zQ49NHnmDV7+IwWL5OlYMp+5vtU4RPBEXUMz16s+qPqBJWxW+kA/WV4zM hzY2wXyvilAXbu+bGQmn8LdHtQiXuvFV6cUAtGB24UPCdSNCscAWELcATSycEmWp ly/BoaMS9tq8Ly8M4ElCN0055Q2vZJH0a7b+JVY3bmfGQ1kynTku2Y498C8xpcNm qvxYQ20IeUuTBQJsjiU+iN6BQ1mjWFlgynOJ7lki9GNKNMweP/SFx7xJUFXyCW4= =Q1Cw -----END PGP SIGNATURE----- --bKyqfOwhbdpXa4YI--