All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Goirand <thomas@goirand.fr>
To: xen-devel@lists.xensource.com
Subject: Re: Monitoring I/O rate for each VMs
Date: Tue, 28 Nov 2006 16:04:34 +0800	[thread overview]
Message-ID: <456BED92.1020807@goirand.fr> (raw)
In-Reply-To: <C1906338.5198%keir@xensource.com>

Keir Fraser wrote:
> On 27/11/06 09:25, "Thomas Goirand" <thomas@goirand.fr> wrote:
> 
>>> Unfortunately these count requests rather than bytes served. This may be
>>> what you want though, as #requests should be proportional to the number of
>>> expensive disc operations (seeking and settling). Long contiguous requests
>>> are not proportionally more expensive than short ones.
>> Hi!
>>
>> I didn't find such file where you said. Even a "locate statistics"
>> didn't help. Note that I'm using lvm partitions, and xen 3.0.2-2 (and
>> 2.0.7 in some older servers), and my LVs are of form /dev/lvm1/xen01, is
>> <path-to-vdb> for loopback?
> 
> I think the stats were added during 3.0.3 development. There's no way to get
> the information you seek with older versions of Xen, although you could try
> taking the blkback driver from a 3.0.3 tree and build it against your Linux
> dom0 kernel.

cat /sys/block/dm-21/stat
8        0       96       95       63        0     4432     1608
0      579     1703

What are the meaning of those numbers ???

Thomas

  reply	other threads:[~2006-11-28  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 21:49 Monitoring I/O rate for each VMs Thomas Goirand
2006-11-27  8:12 ` Keir Fraser
2006-11-27  9:25   ` Thomas Goirand
2006-11-27  9:41     ` Keir Fraser
2006-11-28  8:04       ` Thomas Goirand [this message]
2006-11-28  9:25         ` Muli Ben-Yehuda
2006-11-28 10:51       ` Nick Craig-Wood

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=456BED92.1020807@goirand.fr \
    --to=thomas@goirand.fr \
    --cc=xen-devel@lists.xensource.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 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.