All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andy Burns <xen.lists@burns.me.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Fwd: xentop reporting zero written sectors
Date: Mon, 10 Oct 2011 15:26:50 -0400	[thread overview]
Message-ID: <20111010192650.GA31011@phenom.oracle.com> (raw)
In-Reply-To: <CAE1-PRdorUt+_DznkVe1dgeDJiz5pGe4AGvTkvd=JAN70a=_nQ@mail.gmail.com>

On Mon, Oct 10, 2011 at 07:02:08PM +0100, Andy Burns wrote:
> On 10 October 2011 16:29, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> 
> > How would it be a feature?
> 
> Sorry for the bug <-> feature sarcasm
> 
> > Scrobbling around under tools/xenstat these statistics appear to be read
> > from /sys/bus/xen-backend/devices/<vbd>/wr_sect (likewise rd_sect,
> > wr_req etc etc).
> > Can you see all of those and do the numbers appear to be doing the right
> > thing?
> 
> Yes, just to confirm what Konrad has spotted ...
> 
> # cat /sys/bus/xen-backend/devices/*/statistics/wr_sect
> 0
> 0
> 0
> 
> # cat /sys/bus/xen-backend/devices/*/statistics/rd_sect
> 90313
> 125876
> 2546
> 
> I'll try the patch later, when I've finished pulling my hair out with
> a pci-passthrough issue!

HVM or PV?

  reply	other threads:[~2011-10-10 19:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE1-PRdq9BWjTTHPPBPvESr-ULcdjHgPMTABcCO6+wCLJ1UYog@mail.gmail.com>
2011-10-10 15:16 ` Fwd: xentop reporting zero written sectors Andy Burns
2011-10-10 15:29   ` Ian Campbell
2011-10-10 18:02     ` Andy Burns
2011-10-10 19:26       ` Konrad Rzeszutek Wilk [this message]
2011-10-10 16:31   ` Konrad Rzeszutek Wilk
2011-10-11  7:49     ` Ian Campbell
2011-10-11 15:47       ` Konrad Rzeszutek Wilk
2011-10-13 21:10     ` Andy Burns
2011-10-14  0:20       ` Andy Burns

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=20111010192650.GA31011@phenom.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen.lists@burns.me.uk \
    /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.