[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Nbd] [PATCH v2] doc: Add NBD_CMD_BLOCK_STATUS extensio

From: Paolo Bonzini
Subject: Re: [Qemu-devel] [Nbd] [PATCH v2] doc: Add NBD_CMD_BLOCK_STATUS extension
Date: Tue, 5 Apr 2016 15:41:14 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

On 05/04/2016 01:03, Eric Blake wrote:
> But while Alex and Denis were arguing that no one would ever query both
> things at once (and therefore, it might be better to make
> NBD_STATUS_HOLE and NBD_STATUS_CLEAN both be bit 0), your approach of
> having two separate request flags and allowing both at once would mean
> we do need to keep the status information separate (NBD_STATUS_HOLE is
> bit 0, NBD_STATUS_CLEAN is bit 2).

I agree that querying both is messy.  It would add complication to the
implementation and the usecases are separate enough.

Usually you would first query for dirtiness, and then perhaps ask for
allocation status on the dirty areas.  Getting back the allocation
status on the clean areas would make the request unnecessarily larger.
In addition, querying the dirtiness status should be extremely cheap,
while querying the allocation status might be expensive depending on the
underlying storage.


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]