All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, armbru@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3 1/3] block: add bdrv_get_format_alloc_stat format interface
Date: Thu, 29 Jun 2017 17:44:45 -0400	[thread overview]
Message-ID: <f0927df1-cc55-3fdf-4afb-6c6906ebe053@redhat.com> (raw)
In-Reply-To: <e3d7021b-4c71-50ea-87d3-66de1709161a@virtuozzo.com>


On 06/29/2017 02:59 AM, Vladimir Sementsov-Ogievskiy wrote:
> 29.06.2017 03:15, John Snow wrote:
>>
>> Alright, let me see if I have this straight...
>>
>> used-data: Normal data. We are standing on terra-firma.
>> used-zero: Data that is defined to be zeroes in some way.
>>
>> (Does not necessarily include data clusters if they were not actually
>> zeroed out, I think. May not include regions that ARE zero, even if they
>> are literally zero, because the driver may not especially recognize them
>> as such. Anything marked as zero will DEFINITELY be zero, though. Yes?)
>>
>> used-discarded: I'm not actually sure in this case.
>>
>> used-overrun: Data that is defined to exist, but appears to fall outside
>> of or beyond EOF. Appears to happen with qcow2 metadata before any
>> writes occur.
>>
>> unused-data: Normal data, but not in-use by the schema anywhere. Leaked
>> clusters and the like, effectively.
>>
>> unused-zero: Similar to the above, but definitely zeroes.
>>
>> unused-discarded: Not really sure.
> 
> yes, something like this. again, -data, -zero and -discarded are just
> corresponding to return value of bdrv_get_block_status(bs->file),
> 
> if status & BDRV_BLOCK_DATA
>    it is  -data
> else if status & BDRV_BLOCK_ZERO
>    it is -zero (should be holes for raw)
> else
>    it is -discarded (impossible for raw)
> end
> 

Understood, but I was not too clear on the exact nature of block status,
so I needed to clarify. I'm a lot clearer now, thanks.

  reply	other threads:[~2017-06-29 21:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 16:26 [Qemu-devel] [PATCH v3 0/3] qemu-img check: format allocation info Vladimir Sementsov-Ogievskiy
2017-06-06 16:26 ` [Qemu-devel] [PATCH v3 1/3] block: add bdrv_get_format_alloc_stat format interface Vladimir Sementsov-Ogievskiy
2017-06-26 23:19   ` [Qemu-devel] [Qemu-block] " John Snow
2017-06-28 15:59     ` Vladimir Sementsov-Ogievskiy
2017-06-29  0:15       ` John Snow
2017-06-29  6:59         ` Vladimir Sementsov-Ogievskiy
2017-06-29 21:44           ` John Snow [this message]
2017-06-30  0:27   ` John Snow
2017-06-30  0:45     ` Eric Blake
2017-06-30  0:54       ` John Snow
2017-06-30  1:14         ` Eric Blake
2017-07-12 15:18     ` Vladimir Sementsov-Ogievskiy
2017-07-24 12:45       ` Vladimir Sementsov-Ogievskiy
2017-07-27 21:23       ` John Snow
2017-07-28  8:25         ` Vladimir Sementsov-Ogievskiy
2017-07-28 12:05         ` Eric Blake
2017-06-06 16:26 ` [Qemu-devel] [PATCH v3 2/3] qcow2: add .bdrv_get_format_alloc_stat Vladimir Sementsov-Ogievskiy
2017-06-06 16:26 ` [Qemu-devel] [PATCH v3 3/3] qemu-img check: add format allocation info Vladimir Sementsov-Ogievskiy
2017-06-21 11:08 ` [Qemu-devel] ping Re: [PATCH v3 0/3] qemu-img check: " Vladimir Sementsov-Ogievskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0927df1-cc55-3fdf-4afb-6c6906ebe053@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.