From: Andrew Theurer <habanero@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] turn off writable page tables
Date: Tue, 25 Jul 2006 17:14:27 -0500 [thread overview]
Message-ID: <44C697C3.3090607@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
At OLS I gave a talk on some of the Xen scalability inhibitors, and one
of these was writable page tables. We went over why the feature does
not scale, but just as important, we found that the uniprocessor case
does not provide any advantage either. These tests were done on x86_64,
so I wanted to run the 1-way test on 32 bit to show the same problem.
So, I have run with writable PTs and with emulation forced on for
several benchmarks:
on Xeon MP processor, uniprocessor dom0 kernel, pae=y:
benchmark c/s 10729 force_emulate
------------------------ --------- -------------
lmbench fork+exit: 469.5833 470.3913 usec, lower is better
lmbench fork+execve: 1241.0000 1225.7778 usec, lower is better
lmbench fork+/sbin/bash: 12190.000 12119.000 usec, lower is better
dbench 3.03 186.354 191.278 MB/sec
reaim_aim9 1890.01 2055.97 jobs/min
reaim_compute 2538.75 2522.90 jobs/min
reaim_dbase 3852.14 3739.38 jobs/min
reaim_fserver 4437.93 4389.71 jobs/min
reaim_shared 2365.85 2362.97 jobs/min
SPEC SDET 4315.91 4312.02 scripts/hr
These are all within the noise level (some slightly better, some
slightly worse for emulate). There really isn't much of difference
here. I'd like to propose turning on the emulate path all the time in
xen.
-Andrew Theurer
Applies to c/s 10729
Signed-off-by: Andrew Theurer <habanero@us.ibm.com>
[-- Attachment #2: force-emulate.patch --]
[-- Type: text/x-patch, Size: 493 bytes --]
diff -Naurp xen-unstable.hg-10729/xen/arch/x86/mm.c xen-unstable.hg-10729-emulate/xen/arch/x86/mm.c
--- xen-unstable.hg-10729/xen/arch/x86/mm.c 2006-07-25 17:05:33.000000000 -0500
+++ xen-unstable.hg-10729-emulate/xen/arch/x86/mm.c 2006-07-25 17:03:40.000000000 -0500
@@ -3582,7 +3582,7 @@ int ptwr_do_page_fault(struct domain *d,
return 0;
}
-#if 0 /* Leave this in as useful for debugging */
+#if 1 /* Leave this in as useful for debugging */
goto emulate;
#endif
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-07-25 22:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 22:14 Andrew Theurer [this message]
2006-07-25 22:43 ` [PATCH] turn off writable page tables Nivedita Singhvi
2006-07-25 23:19 ` Andrew Theurer
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 22:41 Ian Pratt
2006-07-26 2:25 ` Andrew Theurer
2006-07-26 5:31 ` Jacob Gorm Hansen
2006-07-26 8:18 ` Gerd Hoffmann
2006-07-26 8:40 ` Keir Fraser
2006-07-26 21:10 ` Andrew Theurer
2006-07-26 21:38 Ian Pratt
2006-07-27 14:43 ` Andrew Theurer
2006-07-27 15:30 ` Keir Fraser
[not found] <E1G5sBV-0005eg-At@host-192-168-0-1-bcn-london>
2006-07-26 23:38 ` Joe Bonasera
2006-07-27 17:31 Ian Pratt
2006-07-28 8:55 ` Keir Fraser
2006-07-28 15:21 ` Andrew Theurer
2006-07-28 15:51 Ian Pratt
2006-07-28 16:31 ` Keir Fraser
2006-07-28 21:36 ` Zachary Amsden
2006-07-28 23:05 ` Andi Kleen
2006-07-28 23:10 ` Zachary Amsden
2006-07-31 9:14 ` Keir Fraser
2006-07-31 9:32 ` Zachary Amsden
2006-07-31 9:53 ` Keir Fraser
2006-07-31 19:56 ` Zachary Amsden
2006-07-31 22:07 ` Keir Fraser
2006-07-31 22:40 ` Zachary Amsden
2006-08-02 9:21 ` Keir Fraser
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=44C697C3.3090607@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.