From: Uri Lublin <uril@redhat.com>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: [Qemu-devel] [PATCH 5/5 v2] qemu-img: info: show highest_alloc and num_free_bytes if exist
Date: Thu, 22 Jan 2009 12:43:55 +0200 [thread overview]
Message-ID: <1232621035-4951-6-git-send-email-uril@redhat.com> (raw)
In-Reply-To: <1232621035-4951-5-git-send-email-uril@redhat.com>
Signed-off-by: Uri Lublin <uril@redhat.com>
---
qemu-img.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index 555ab5f..41ff13b 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -727,6 +727,10 @@ static int img_info(int argc, char **argv)
if (bdrv_get_info(bs, &bdi) >= 0) {
if (bdi.cluster_size != 0)
printf("cluster_size: %d\n", bdi.cluster_size);
+ if (bdi.highest_alloc)
+ printf("highest_alloc: %ld\n", bdi.highest_alloc);
+ if (bdi.num_free_bytes)
+ printf("num_free_bytes: %ld\n", bdi.num_free_bytes);
}
bdrv_get_backing_filename(bs, backing_filename, sizeof(backing_filename));
if (backing_filename[0] != '\0') {
--
1.6.0.6
next prev parent reply other threads:[~2009-01-22 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 10:43 [Qemu-devel] [PATCH 0/5 v2] qcow2 info: show highest-allocation and num-free-bytes Uri Lublin
2009-01-22 10:43 ` [Qemu-devel] [PATCH 1/5 v2] block-qcow2: keep highest allocated byte Uri Lublin
2009-01-22 10:43 ` [Qemu-devel] [PATCH 2/5 v2] block-qcow2: export highest_allocated through BlockDriverInfo and get_info() Uri Lublin
2009-01-22 10:43 ` [Qemu-devel] [PATCH 3/5 v2] info blockstats: show highest_allocated if exists Uri Lublin
2009-01-22 10:43 ` [Qemu-devel] [PATCH 4/5 v2] qcow2 format: keep 'num_free_bytes', and show it upon 'info blockstats' Uri Lublin
2009-01-22 10:43 ` Uri Lublin [this message]
2009-01-22 18:58 ` [Qemu-devel] [PATCH 0/5 v2] qcow2 info: show highest-allocation and num-free-bytes Anthony Liguori
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=1232621035-4951-6-git-send-email-uril@redhat.com \
--to=uril@redhat.com \
--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).