From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Richard W.M. Jones" <rjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 'info blockstats' to collect block device statistics
Date: Mon, 03 Dec 2007 21:58:05 +0200 [thread overview]
Message-ID: <47545FCD.5060600@qumranet.com> (raw)
In-Reply-To: <475455F7.4090407-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Richard W.M. Jones wrote:
> I wonder if KVM would be interested in taking my QEMU patch to support
> block device statistics.
>
> This patch collects per-block-device statistics and allows them to be
> displayed in the monitor through a 'info blockstats' command. It
> generalises the VMDK-only support for this which was added to KVM's
> version of QEMU.
>
> Proposed patch:
> http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00770.html
>
> Accepted into QEMU:
> http://lists.gnu.org/archive/html/qemu-devel/2007-12/msg00013.html
>
> The QEMU patch doesn't quite apply directly because KVM has no file
> qemu/block.h. Attached is a rebased patch against the current
> kvm-userspace.
>
> Rich.
>
we will do merge with qemu cvs soon (i hope) and it probably will be the
best way to apply your patch
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
prev parent reply other threads:[~2007-12-03 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 19:16 'info blockstats' to collect block device statistics Richard W.M. Jones
[not found] ` <475455F7.4090407-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-12-03 19:58 ` Izik Eidus [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=47545FCD.5060600@qumranet.com \
--to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 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.