From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36327) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R44nP-00037c-Ei for qemu-devel@nongnu.org; Thu, 15 Sep 2011 01:47:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R44nO-0000iS-Ay for qemu-devel@nongnu.org; Thu, 15 Sep 2011 01:47:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24110) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R44nO-0000fu-2K for qemu-devel@nongnu.org; Thu, 15 Sep 2011 01:47:34 -0400 Date: Thu, 15 Sep 2011 08:47:29 +0300 From: Gleb Natapov Message-ID: <20110915054729.GV21417@redhat.com> References: <4E70DEE8.8090908@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E70DEE8.8090908@linux.vnet.ibm.com> Subject: Re: [Qemu-devel] Design of the blobstore List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Berger Cc: Markus Armbruster , Anthony Liguori , QEMU Developers , "Michael S. Tsirkin" On Wed, Sep 14, 2011 at 01:05:44PM -0400, Stefan Berger wrote: > One property of the blobstore is that it has a certain required > size for accommodating all blobs of device that want to store their > blobs onto. The assumption is that the size of these blobs is know > a-priori to the writer of the device code and all devices can > register their space requirements with the blobstore during device > initialization. Then gathering all the registered blobs' sizes plus > knowing the overhead of the layout of the data on the disk lets QEMU > calculate the total required (minimum) size that the image has to > have to accommodate all blobs in a particular blobstore. > I do not see the point of having one blobstore for all devices. Each should have its own. We will need permanent storage for UEFI firmware too and creating new UEFI config for each machine configuration is not the kind of usability we want to have. -- Gleb.