From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49389) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Spbvs-0008Gk-Fs for qemu-devel@nongnu.org; Fri, 13 Jul 2012 05:13:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Spbvq-0006vP-8M for qemu-devel@nongnu.org; Fri, 13 Jul 2012 05:13:04 -0400 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:32825) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Spbvp-0006up-W5 for qemu-devel@nongnu.org; Fri, 13 Jul 2012 05:13:02 -0400 Received: from /spool/local by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 13 Jul 2012 10:12:59 +0100 Received: from d06av07.portsmouth.uk.ibm.com (d06av07.portsmouth.uk.ibm.com [9.149.37.248]) by d06nrmr1707.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6D9CmZu2523256 for ; Fri, 13 Jul 2012 10:12:48 +0100 Received: from d06av07.portsmouth.uk.ibm.com (d06av07.portsmouth.uk.ibm.com [127.0.0.1]) by d06av07.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6D8sRls022077 for ; Fri, 13 Jul 2012 04:54:27 -0400 Date: Fri, 13 Jul 2012 10:12:47 +0100 From: Stefan Hajnoczi Message-ID: <20120713091247.GA15503@stefanha-thinkpad.localdomain> References: <4FFA9C30.2070201@linux.vnet.ibm.com> <20120709092705.GG16198@redhat.com> <4FFBBF8C.8080708@linux.vnet.ibm.com> <4FFBD729.8000309@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FFBD729.8000309@redhat.com> Subject: Re: [Qemu-devel] [RFC] introduce a dynamic library to expose qemu block API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , Wenchao Xia , qemu-devel@nongnu.org On Tue, Jul 10, 2012 at 09:18:01AM +0200, Paolo Bonzini wrote: > Il 10/07/2012 07:37, Wenchao Xia ha scritto: > >> > >> For getting the other metadata about the disk image you mention, another > >> possibility to is just make 'qemu-img info' return the data in a machine > >> parseable format, ie JSON& make a client API for extracting data from > >> this JSON document. > >> > > Thank u for the idea. The .so is introduced to let program access the > > image more directly, parsing string is not so fast and it depends on > > another program's stdout output, I hope to get a faster way. > > I doubt you actually have profiled it. I think speed is not the issue, instead it's just providing an API that external programs can use. Management tools, backup software, custom administration tools, etc. It's convenient to have an API. Stefan