From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48287) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TOm3D-0004Pp-HT for qemu-devel@nongnu.org; Thu, 18 Oct 2012 05:06:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TOm3A-0003w7-RJ for qemu-devel@nongnu.org; Thu, 18 Oct 2012 05:05:59 -0400 Received: from nodalink.pck.nerim.net ([62.212.105.220]:49192 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TOm3A-0003vc-Js for qemu-devel@nongnu.org; Thu, 18 Oct 2012 05:05:56 -0400 Date: Thu, 18 Oct 2012 11:06:00 +0200 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20121018090600.GB3958@irqsave.net> References: <1350489629-1838-1-git-send-email-benoit@irqsave.net> <1350489629-1838-2-git-send-email-benoit@irqsave.net> <507EDCC0.4050703@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <507EDCC0.4050703@redhat.com> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC V2 01/20] qcow2: Add deduplication to the qcow2 specification. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com > That's still too sparse for a formal documentation - what is the format > of the deduplication table, and what do the bits in that table imply > with regards to how the rest of the qcow2 file is used? I will add this in the next iteration. Best regards Beno=EEt