From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36460 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PObl2-0004Qo-QM for qemu-devel@nongnu.org; Fri, 03 Dec 2010 14:57:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PObl1-0006Gs-8D for qemu-devel@nongnu.org; Fri, 03 Dec 2010 14:57:28 -0500 Received: from mail-qw0-f45.google.com ([209.85.216.45]:51306) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PObl1-0006Gn-5K for qemu-devel@nongnu.org; Fri, 03 Dec 2010 14:57:27 -0500 Received: by qwc9 with SMTP id 9so574574qwc.4 for ; Fri, 03 Dec 2010 11:57:23 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4CF90727.7000507@codemonkey.ws> References: <1291374593-17448-1-git-send-email-ronniesahlberg@gmail.com> <4CF90727.7000507@codemonkey.ws> Date: Sat, 4 Dec 2010 06:57:23 +1100 Message-ID: Subject: Re: [Qemu-devel] [Patch 0/14] builtin iscsi support From: ronnie sahlberg Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org On Sat, Dec 4, 2010 at 2:05 AM, Anthony Liguori wrote: > On 12/03/2010 05:09 AM, ronniesahlberg@gmail.com wrote: >> >> Note that ./block/iscsi/* is aimed at being re-used outisde of qemu/kvm >> in other applications why qemu/kvm specific calkls are not used there. >> > > So should the library be packaged outside of QEMU and then we'll just link > against it? Eventually I guess. But that would take a long time before it is ready for standalone distrution. I see this as similar to the situation with LIBTALLOC and LIBTDB that originated from samba. For many years these libraries were kept as local copies inside the source trees of many projects, including samba3, samba4, ctdb, openchange, etc where the tdb/talloc maintainers merged patches and fixes across the different comsumer projects manually. While these libraries are now at a stage where they are mature enough to stand on their own, they now start to appear as separate standalone packages for distros. So in time, once all distros ship them as standalone the local copies held in some of the projects may be removed and replaced with linking with the standalone library instead. I see that as one possible path how a library is started to be used, how it evolves and once proven and mature enough it becomes a standalone package. Do you see a problem with that path and/or would you want that path not to be used in qemu/kvm ? While the library is complete enough for the use and the features that qemu/kvm needs, I think there are a lot of work in other areas that kvm/qemu does not need/use before it can become standalone. regards ronnie sahlberg