From: Rik van Riel <riel@redhat.com>
To: Michael Wolf <mjw@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
peterz@infradead.org, mtosatti@redhat.com, glommer@parallels.com,
mingo@redhat.com, avi@redhat.com, anthony@codemonkey.ws
Subject: Re: [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time.
Date: Mon, 22 Oct 2012 11:33:52 -0400 [thread overview]
Message-ID: <50856760.2030507@redhat.com> (raw)
In-Reply-To: <20121017022249.16949.2775.stgit@lambeau>
On 10/16/2012 10:23 PM, Michael Wolf wrote:
> In the case of where you have a system that is running in a
> capped or overcommitted environment the user may see steal time
> being reported in accounting tools such as top or vmstat. This can
> cause confusion for the end user.
How do s390 and Power systems deal with reporting that kind
of information?
IMHO it would be good to see what those do, so we do not end
up re-inventing the wheel, and confusing admins with yet another
way of reporting the information...
--
All rights reversed
next prev parent reply other threads:[~2012-10-22 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 2:23 [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 1/5] Alter the amount of steal time reported by the guest Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 2/5] Expand the steal time msr to also contain the consigned time Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 3/5] Add the code to send the consigned time from the host to the guest Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 4/5] Add a timer to allow the separation of consigned from steal time Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 5/5] Add an ioctl to communicate the consign limit to the host Michael Wolf
2012-10-17 17:14 ` [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time Glauber Costa
2012-10-17 15:13 ` Michael Wolf
2012-10-22 15:33 ` Rik van Riel [this message]
2012-11-26 20:00 ` Michael Wolf
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=50856760.2030507@redhat.com \
--to=riel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=glommer@parallels.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjw@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).