From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: eblake@redhat.com, armbru@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, vsementsov@virtuozzo.com, den@openvz.org
Subject: [Qemu-devel] [PATCH v3 1/3] block: add bdrv_get_format_alloc_stat format interface
Date: Tue, 6 Jun 2017 19:26:50 +0300 [thread overview]
Message-ID: <20170606162652.112122-2-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20170606162652.112122-1-vsementsov@virtuozzo.com>
The function should collect statistics, about used/unused by top-level
format driver space (in its .file) and allocation status
(data/zero/discarded/after-eof) of corresponding areas in this .file.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
block.c | 16 ++++++++++++++
include/block/block.h | 3 +++
include/block/block_int.h | 2 ++
qapi/block-core.json | 55 +++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 76 insertions(+)
diff --git a/block.c b/block.c
index 50ba264143..7d720ae0c2 100644
--- a/block.c
+++ b/block.c
@@ -3407,6 +3407,22 @@ int64_t bdrv_get_allocated_file_size(BlockDriverState *bs)
}
/**
+ * Collect format allocation info. See BlockFormatAllocInfo definition in
+ * qapi/block-core.json.
+ */
+int bdrv_get_format_alloc_stat(BlockDriverState *bs, BlockFormatAllocInfo *bfai)
+{
+ BlockDriver *drv = bs->drv;
+ if (!drv) {
+ return -ENOMEDIUM;
+ }
+ if (drv->bdrv_get_format_alloc_stat) {
+ return drv->bdrv_get_format_alloc_stat(bs, bfai);
+ }
+ return -ENOTSUP;
+}
+
+/**
* Return number of sectors on success, -errno on error.
*/
int64_t bdrv_nb_sectors(BlockDriverState *bs)
diff --git a/include/block/block.h b/include/block/block.h
index 9b355e92d8..646376a772 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -335,6 +335,9 @@ typedef enum {
int bdrv_check(BlockDriverState *bs, BdrvCheckResult *res, BdrvCheckMode fix);
+int bdrv_get_format_alloc_stat(BlockDriverState *bs,
+ BlockFormatAllocInfo *bfai);
+
/* The units of offset and total_work_size may be chosen arbitrarily by the
* block driver; total_work_size may change during the course of the amendment
* operation */
diff --git a/include/block/block_int.h b/include/block/block_int.h
index 8d3724cce6..458c715e99 100644
--- a/include/block/block_int.h
+++ b/include/block/block_int.h
@@ -208,6 +208,8 @@ struct BlockDriver {
int64_t (*bdrv_getlength)(BlockDriverState *bs);
bool has_variable_length;
int64_t (*bdrv_get_allocated_file_size)(BlockDriverState *bs);
+ int (*bdrv_get_format_alloc_stat)(BlockDriverState *bs,
+ BlockFormatAllocInfo *bfai);
int coroutine_fn (*bdrv_co_pwritev_compressed)(BlockDriverState *bs,
uint64_t offset, uint64_t bytes, QEMUIOVector *qiov);
diff --git a/qapi/block-core.json b/qapi/block-core.json
index ea0b3e8b13..fd7b52bd69 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -139,6 +139,61 @@
'*format-specific': 'ImageInfoSpecific' } }
##
+# @BlockFormatAllocInfo:
+#
+#
+# Allocation relations between format file and underlying protocol file.
+# All fields are in bytes.
+#
+# There are two types of the format file portions: 'used' and 'unused'. It's up
+# to the format how to interpret these types. For now the only format supporting
+# the feature is Qcow2 and for this case 'used' are clusters with positive
+# refcount and unused a clusters with zero refcount. Described portions include
+# all format file allocations, not only virtual disk data (metadata, internal
+# snapshots, etc. are included).
+#
+# For the underlying file there are native block-status types of the portions:
+# - data: allocated data
+# - zero: read-as-zero holes
+# - discarded: not allocated
+# 4th additional type is 'overrun', which is for the format file portions beyond
+# the end of the underlying file.
+#
+# So, the fields are:
+#
+# @used-data: used by the format file and backed by data in the underlying file
+#
+# @used-zero: used by the format file and backed by a hole in the underlying
+# file
+#
+# @used-discarded: used by the format file but actually unallocated in the
+# underlying file
+#
+# @used-overrun: used by the format file beyond the end of the underlying file
+#
+# @unused-data: allocated data in the underlying file not used by the format
+#
+# @unused-zero: holes in the underlying file not used by the format file
+#
+# @unused-discarded: unallocated areas in the underlying file not used by the
+# format file
+#
+# Note: sum of 6 fields {used,unused}-{data,zero,discarded} is equal to the
+# length of the underlying file.
+#
+# Since: 2.10
+#
+##
+{ 'struct': 'BlockFormatAllocInfo',
+ 'data': {'used-data': 'uint64',
+ 'used-zero': 'uint64',
+ 'used-discarded': 'uint64',
+ 'used-overrun': 'uint64',
+ 'unused-data': 'uint64',
+ 'unused-zero': 'uint64',
+ 'unused-discarded': 'uint64' } }
+
+##
# @ImageCheck:
#
# Information about a QEMU image file check
--
2.11.1
next prev parent reply other threads:[~2017-06-06 16:27 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 ` Vladimir Sementsov-Ogievskiy [this message]
2017-06-26 23:19 ` [Qemu-devel] [Qemu-block] [PATCH v3 1/3] block: add bdrv_get_format_alloc_stat format interface 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
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=20170606162652.112122-2-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).