WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] linux/i386: allow CONFIG_HIGHPTE on i386 (take 2

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] linux/i386: allow CONFIG_HIGHPTE on i386 (take 2)
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 12 Jan 2007 10:26:49 +0000
Delivery-date: Fri, 12 Jan 2007 02:26:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45A51A07.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acc2NCrxaZu2oqInEdu5iwAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] linux/i386: allow CONFIG_HIGHPTE on i386 (take 2)
User-agent: Microsoft-Entourage/11.2.5.060620


On 10/1/07 15:53, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> While, as discussed, the performance impact of this option is certainly higher
> than on native Linux, the option should not be entirely disallowed if people
> want to sacrifice performance for less lowmem pressure.
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Much of the suckiness will come from the fact that highptes are being pinned
for their lifetime. This means that you don't avoid emulation traps for
updates during process fork() and exit(), which are big wins. Obviously  the
problem is that kmap_atomic_pte() doesn't know whether to map the page
writeable or read-only (is it part of a pinned pagetable yet?). We could
steal a page flag, or use page->private, or something like that do give this
info... This patch is fine for now though.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>