Re: [Qemu-devel] [RFC] Proposed qcow2 extension: subcluster allocation

From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Alberto Garcia <berto@igalia.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Proposed qcow2 extension: subcluster allocation
Date: Tue, 11 Apr 2017 10:30:03 -0500	[thread overview]
Message-ID: <be491b99-9ea4-d1d0-41f4-51945b64f5d4@redhat.com> (raw)
In-Reply-To: <760cb82c-9bff-c289-c2b3-940319c66b5c@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On 04/11/2017 10:18 AM, Max Reitz wrote:

> Hm, yeah, although you have to keep in mind that the padding is almost
> pretty much the same as the the data bits we need, effectively doubling
> the size of the L2 tables:
> 
> padding = 2^{n+2} - 2^{n+1} - 64 (=2^6)
>         = 2^{n+1} - 64
> 
> So that's not so nice, but if it's the only thing we can do...

Or we mix-and-match your ideas: since our subclusters are ternary
encoding, if you want 128 subclusters, instead of asking for 256 bits,
you ask for ld(3^128) = 203 bits, then use 11 padding bits of your
original 64, and you have something that still fits in 256 bits instead
of 512...

Okay, just kidding.  Anything larger than 32 subclusters does get
awkward fast.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]