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] x86: don't map more than the allocated spacefor

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] x86: don't map more than the allocated spacefor frame_table
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 20 May 2009 15:47:33 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 20 May 2009 07:47:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C6395A04.6AC1%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4A1421A80200007800001CB1@xxxxxxxxxxxxxxxxxx> <C6395A04.6AC1%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 20.05.09 15:56 >>>
>On 20/05/2009 06:28, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>
>> Also, make frame_table a 'mostly read' variable. Actually, I don't
>> really understand why this has to be a variable on x86 at all -
>> address calculations involving it could be cheaper if this was just
>> a #define. Perhaps kexec is the only thing that needs this to be a
>> variable, but if that indeed is the only reason, kexec should define
>> its own static variable.
>
>Would it really be much cheaper? Pointer load versus a 64-bit constant? If
>you're sure it would be an improvement I would take a patch.

Certainly not much (especially with it now sitting in __read_mostly), but the
official latencies are still <= 1 vs >= 2, and additionally memory clobbers
wouldn't matter anymore for the compiler's scheduling decisions.

Since I wasn't sure, I didn't submit a patch right away...

Jan


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

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