qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5 v2] qcow2 info: show highest-allocation and	num-free-bytes
Date: Thu, 22 Jan 2009 12:58:12 -0600	[thread overview]
Message-ID: <4978C1C4.8080709@us.ibm.com> (raw)
In-Reply-To: <1232621035-4951-1-git-send-email-uril@redhat.com>

Uri Lublin wrote:
> Hello,
>
> The following 5 enhance "info blockstats" for qcow2 images (and
> other formats that implement bdrv_get_info), to show 
> higest-allocated-offset and number-of-free-bytes (below
> the higest-allocated-offset) of the image.
>
> One of the main usage for this information is to know and act
> upon a case of end-of-storage-space. Instead of waiting for
> -ENOSPACE (which now may cause the VM to stop), one can
> define a threshold and extend the diskspace allocated for
> the image.
> This info is also good for management systems, so they
> can report the user disk space status.
>
> Also with highest_alloc and num_free_bytes, we can have a pretty 
> good idea about how fragmented a qcow2 images is, and try to
> defragment it later.
>
> Patches 1,2,3, Provides information about the highest allocated byte (offset)
> Patch 4, Provides information about the number of free bytes 
>          below highest_alloc.
> Patch 5, Provides info about highest_alloc and num_free_bytes through 
>          qemu-img info
>
>
> Changes from v1: better description of use cases.
>   

Applied all.  Thanks.

Regards,

Anthony Liguori

> Regards,
>     Uri.
>
>
>
>   

      parent reply	other threads:[~2009-01-22 18:58 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         ` [Qemu-devel] [PATCH 5/5 v2] qemu-img: info: show highest_alloc and num_free_bytes if exist Uri Lublin
2009-01-22 18:58 ` Anthony Liguori [this message]

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=4978C1C4.8080709@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=uril@redhat.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 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).