From: Michael Vrable <mvrable@cs.ucsd.edu>
To: xen-devel@lists.sourceforge.net
Subject: Re: VM Remote access options
Date: Tue, 28 Sep 2004 11:19:00 -0700 [thread overview]
Message-ID: <20040928111900.B18973@cs.ucsd.edu> (raw)
In-Reply-To: <415a61ee.3ccb.0@australia.edu>; from tcranbrook@australia.edu on Tue, Sep 28, 2004 at 11:45:39AM -0400
On Tue, Sep 28, 2004 at 11:45:39AM -0400, Tom Cranbrook wrote:
> The top command shows several new items in the cpu summary display for a
> running domain, labeled wa, hi, and si. Can't find any docs refs to them.
> Know want those are?
wa = I/O wait; time when the CPU is idle but a process is blocked
waiting for data
hi = hardware interrupts
si = softirq interrupts
(A bit of digging turned up help in Documentation/filesystems/proc.txt
in the kernel source tree. Look in the section "1.8 Miscellaneous
kernel statistics in /proc/stat".)
--Michael Vrable
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-09-28 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 15:45 VM Remote access options Tom Cranbrook
2004-09-28 16:15 ` Ian Pratt
2004-09-28 17:06 ` Mark A. Williamson
2004-09-28 18:19 ` Michael Vrable [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 20:48 Tom Cranbrook
2004-09-28 20:53 Tom Cranbrook
2004-09-28 21:13 ` Mark A. Williamson
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=20040928111900.B18973@cs.ucsd.edu \
--to=mvrable@cs.ucsd.edu \
--cc=xen-devel@lists.sourceforge.net \
/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.