From: Andrew Theurer <habanero@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: scaling problem with writable pagetables
Date: Thu, 16 Feb 2006 07:41:37 -0600 [thread overview]
Message-ID: <43F48111.30201@us.ibm.com> (raw)
In-Reply-To: <6cc7be0ec36293dac6b8549c25e9d0be@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 15 Feb 2006, at 18:49, Andrew Theurer wrote:
>
>> Below are per-function ratios of CPU time
>> rev8830/rev8830-lock-reduction (derived from oprofile diffs)
>>
>> SDET:
>>
>> 9.84/1 restore_all_guest
>
> Kind of odd, since that function contains no locking. Perhaps VCPUs
> are blocked so long that, by the time they get the CPU there is an
> event pending and the hypercall gets preempted?
I was a bit surprised at that, too.
>
> What do the perfctr numbers look like for #hypercalls and #exceptions?
> Also worth adding one to __hypercall_create_continuation as that'll
> count #preemptions.
I have not taken perfctr numbers yet, but I will today. Thanks,
-Andrew
prev parent reply other threads:[~2006-02-16 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 18:49 scaling problem with writable pagetables Andrew Theurer
2006-02-16 8:54 ` Keir Fraser
2006-02-16 13:41 ` Andrew Theurer [this message]
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=43F48111.30201@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.