From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54751) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXpsP-0001I4-0r for qemu-devel@nongnu.org; Thu, 11 Aug 2016 09:18:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bXpsK-00008j-3V for qemu-devel@nongnu.org; Thu, 11 Aug 2016 09:18:23 -0400 Date: Thu, 11 Aug 2016 15:18:11 +0200 From: Kevin Wolf Message-ID: <20160811131811.GF5035@noname.redhat.com> References: <1470668720-211300-1-git-send-email-vsementsov@virtuozzo.com> <1470668720-211300-9-git-send-email-vsementsov@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1470668720-211300-9-git-send-email-vsementsov@virtuozzo.com> Subject: Re: [Qemu-devel] [PATCH 08/29] qcow2-bitmap: delete bitmap from qcow2 after load List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Sementsov-Ogievskiy Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com, armbru@redhat.com, eblake@redhat.com, jsnow@redhat.com, famz@redhat.com, den@openvz.org, stefanha@redhat.com, pbonzini@redhat.com Am 08.08.2016 um 17:04 hat Vladimir Sementsov-Ogievskiy geschrieben: > If we load bitmap for r/w bds, it's data in the image should be > considered inconsistent from this point. Therefore it is safe to remove > it from the image. > > Signed-off-by: Vladimir Sementsov-Ogievskiy The approach that you're taking (keeping the complete bitmap directory in memory in its on-disk format) means that we can't keep pointers to a QCow2BitmapHeader anywhere because modifying the directory would move it around. Did you consider using a different in-memory representation like a normal list of structs? This would also allow you to use the normal list iteration mechanisms (i.e. the existing *_FOREACH macros) instead of the rather complex ones you need now. For example, qcow2 snapshots use a different on-disk and in-memory format and the on-disk format is only implemented in the actual read/write functions, and anything else can deal with the simpler in-memory structures. Kevin