linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher Yeoh" <cyeoh@samba.org>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: Chris Yeoh <yeohc@au1.ibm.com>,
	Bryan Rosenburg <rosnbrg@us.ibm.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: Collecting hypervisor call stats
Date: Wed, 7 Jun 2006 11:08:12 +1000	[thread overview]
Message-ID: <17542.9980.803879.151529@localhost.localdomain> (raw)
In-Reply-To: <20060606164646.GA3161@w-mikek2.ibm.com>

At 2006/6/6 09:46-0700  Mike Kravetz writes:
> On Thu, Jun 01, 2006 at 03:12:15PM +1000, Christopher Yeoh wrote:
> > Here's a patch we've used for collecting hcall counts and times.
> 
> Thanks for the patch/code Chris!  I'm using this as a basis for something
> that we may want to merge into the tree.  Just a couple of questions.
> 
> Your 'wrappers' have the following general form:
> 
> 
> Can you explain the need for barrier(s) before and after the call to the
> real routine?  It usually takes me a couple days of thought to figure out
> exactly where these are needed. :)

Ah oops, it turns out I was wrong and they're not necessary after all.

> The use of get_cpu_var/put_cpu_var result in disabling/enabling preemption.
> I can understand why this would be desirable to assure the accuracy of the
> statistics.  But, I was wondering if the desired accuracy is worth the added
> overhead.  My thought was to make these as lightweight as possible and
> sacrifice some accuracy if necessary.  After all, no 'internal decisions' are
> being made because of this data.  It is simply exposed to user land.
> Thoughts?

For what we were using them for at the time we weren't really
concerned about a small degradation in performance and were more
interested in accuracy. I guess I'd recommend doing some benchmarking
to see what difference they really make.

Chris
-- 
cyeoh@au.ibm.com
IBM OzLabs Linux Development Group
Canberra, Australia

  reply	other threads:[~2006-06-07  1:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 20:41 Collecting hypervisor call stats Mike Kravetz
2006-05-31 21:25 ` Geoff Levand
2006-05-31 22:40 ` Paul Mackerras
2006-05-31 22:58   ` Mike Kravetz
2006-06-01  5:26     ` Benjamin Herrenschmidt
2006-06-01 18:14       ` Arnd Bergmann
2006-06-01 21:57         ` Benjamin Herrenschmidt
2006-06-01  4:34 ` Jimi Xenidis
2006-06-01  5:12   ` Christopher Yeoh
2006-06-06 16:46     ` Mike Kravetz
2006-06-07  1:08       ` Christopher Yeoh [this message]
2006-06-07 22:57       ` Segher Boessenkool

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=17542.9980.803879.151529@localhost.localdomain \
    --to=cyeoh@samba.org \
    --cc=kravetz@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rosnbrg@us.ibm.com \
    --cc=yeohc@au1.ibm.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 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).