From: Andrew Theurer <habanero@us.ibm.com>
To: Xen development list <xen-devel@lists.xensource.com>
Subject: Why is 'emulate' as good as writable PT's?
Date: Mon, 05 Jun 2006 16:45:50 -0500 [thread overview]
Message-ID: <4484A60E.6070008@us.ibm.com> (raw)
We have been doing some scalability work, and we noticed that forcing
'emulate' in arch.x86/mm.c achieves the same performance on 1-way dom0.
For example:
xen-unstable, changeset 10200, i386 with PAE, 1-way
benchmark xen0 xen0+emulate
------------- ---- ----
reaim_fserver 4421 4426
reaim_compute 2555 2531
SDET 4759 4810
The reaim benchmarks probably don't have much fork(), where I'd expect
writable page tables to help, but SDET has a ton of fork+exec.
Could there be situations were we are inadvertently triggering a
writable page table, where we should just be doing a update_va_mapping()?
-Andrew
next reply other threads:[~2006-06-05 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 21:45 Andrew Theurer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 22:17 Why is 'emulate' as good as writable PT's? Ian Pratt
2006-06-05 22:29 ` Andrew Theurer
2006-06-06 20:28 ` Andrew Theurer
2006-06-06 21:14 ` Keir Fraser
2006-06-06 22:02 ` Andrew Theurer
2006-06-08 16:05 ` Andrew Theurer
2006-06-12 9:15 Ian Pratt
2006-06-13 14:47 ` Andrew Theurer
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=4484A60E.6070008@us.ibm.com \
--to=habanero@us.ibm.com \
--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.