From: Andrew Theurer <habanero@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Xen development list <xen-devel@lists.xensource.com>,
Rolf Neugebauer <rn@acm.org>
Subject: Re: Why is 'emulate' as good as writable PT's?
Date: Tue, 06 Jun 2006 17:02:02 -0500 [thread overview]
Message-ID: <4485FB5A.6020903@us.ibm.com> (raw)
In-Reply-To: <b40d0941f5d4c3bd6fc0ad79fc0503d6@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 6 Jun 2006, at 21:28, Andrew Theurer wrote:
>
>> Yes, we definitely have a problem here. Tons of flushes with
>> modified=1, and lots with <=10. The three benchmarks all seem to hit
>> the same areas. Here is the output from running SDET, with snippets
>> from System.map mixed in:
>
> Is this PAE? SMP guest?
>
> Do you know much about the SDET benchmark? For example, do you know
> how big the mprotect() calls it makes are likely to be? If vma's are
> small and fairly sparse then the writable pagetable batching won't be
> a win.
1-way SMP kernel, PAE. not sure about the mprotect() calls. SDET
basically calls a lot of utilities like ps, gcc, ispell, etc. Is it
feasible to "xen-ify" unmap_vmas() and copy_page_range(), such that we
use explicit hypercalls instead of faulting on the writes?
-Andrew
next prev parent reply other threads:[~2006-06-06 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-06-08 16:05 ` Andrew Theurer
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 9:15 Ian Pratt
2006-06-13 14:47 ` Andrew Theurer
2006-06-05 21:45 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=4485FB5A.6020903@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rn@acm.org \
--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.