Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-27 Thread Alberto Garcia
> Note that L1 and L2 fields both stop at bit 55 currently, but do have > room for expansion up to bit 61; so all three limits (if we include > refcount table in the set capped at bit 55 for now) could be raised > simultaneously if we find 64P too small in the future. 64 petabytes ought to be

Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-27 Thread Eric Blake
On 02/27/2018 05:47 AM, Kevin Wolf wrote: Am 22.02.2018 um 16:59 hat Eric Blake geschrieben: Although off_t permits up to 63 bits (8EB) of file offsets, in practice, we're going to hit other limits first. Document some of those limits in the qcow2 spec, and how choice of cluster size can

Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-27 Thread Kevin Wolf
Am 22.02.2018 um 16:59 hat Eric Blake geschrieben: > Although off_t permits up to 63 bits (8EB) of file offsets, in > practice, we're going to hit other limits first. Document some > of those limits in the qcow2 spec, and how choice of cluster size > can influence some of the limits. > > While

Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-26 Thread Alberto Garcia
On Mon 26 Feb 2018 05:41:54 PM CET, Eric Blake wrote: >> But refcount blocks are not addressed by L2 tables, so in principle >> it should be possible to have refcount blocks after the first 64PB. > > But (if we don't make this change) that's about all you can usefully > have (and it would be a

Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-26 Thread Eric Blake
On 02/26/2018 10:25 AM, Alberto Garcia wrote: On Thu 22 Feb 2018 04:59:20 PM CET, Eric Blake wrote: While at it, notice that since we cannot map any virtual cluster to any address higher than 64 PB (56 bits) (due to the L1/L2 field encoding), it makes little sense to require the refcount table

Re: [Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-26 Thread Alberto Garcia
On Thu 22 Feb 2018 04:59:20 PM CET, Eric Blake wrote: > While at it, notice that since we cannot map any virtual cluster to > any address higher than 64 PB (56 bits) (due to the L1/L2 field > encoding), it makes little sense to require the refcount table to > access host offsets beyond that point.

[Qemu-block] [PATCH v3 2/4] qcow2: Document some maximum size constraints

2018-02-22 Thread Eric Blake
Although off_t permits up to 63 bits (8EB) of file offsets, in practice, we're going to hit other limits first. Document some of those limits in the qcow2 spec, and how choice of cluster size can influence some of the limits. While at it, notice that since we cannot map any virtual cluster to