From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH] virtio-blk: Add stats VQ to collect information about devices
Date: Thu, 18 Aug 2011 07:38:03 +0300 [thread overview]
Message-ID: <1313642283.22532.4.camel@lappy> (raw)
In-Reply-To: <4E4C481A.5080205@redhat.com>
On Wed, 2011-08-17 at 16:00 -0700, Avi Kivity wrote:
> On 08/16/2011 12:47 PM, Sasha Levin wrote:
> > This patch adds support for an optional stats vq that works similary to the
> > stats vq provided by virtio-balloon.
> >
> > The purpose of this change is to allow collection of statistics about working
> > virtio-blk devices to easily analyze performance without having to tap into
> > the guest.
> >
> >
>
> Why can't you get the same info from the host? i.e. read sectors?
Some of the stats you can collect from the host, but some you can't.
The ones you can't include all the timing statistics and the internal
queue statistics (read/write merges).
The idea behind providing all of the stats on the stats vq (which is
basically what you see in '/dev/block/[device]/stats') is to give a
consistent snapshot of the state of the device.
>
> Patches to virtio drivers should be preceded by specification updates so
> that guest driver authors and alternative userspace developers have a
> solid reference.
>
I'll send an additional update to the spec.
--
Sasha.
next prev parent reply other threads:[~2011-08-18 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 19:47 [PATCH] virtio-blk: Add stats VQ to collect information about devices Sasha Levin
2011-08-17 23:00 ` Avi Kivity
2011-08-18 4:38 ` Sasha Levin [this message]
2011-08-18 15:10 ` Avi Kivity
2011-08-18 16:29 ` Sasha Levin
2011-08-18 17:36 ` Avi Kivity
2011-08-18 17:59 ` Sasha Levin
2011-08-18 18:30 ` Avi Kivity
2011-08-21 23:31 ` 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=1313642283.22532.4.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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