xen-devel

[Top] [All Lists]

[Xen-devel] Re: next->vcpu_dirty_cpumask checking at the top of context

from [Jan Beulich]

[Permanent Link][Original]

To:	<keir.fraser@xxxxxxxxxxxxx>
Subject:	[Xen-devel] Re: next->vcpu_dirty_cpumask checking at the top of context_switch()
From:	"Jan Beulich" <jbeulich@xxxxxxxxxx>
Date:	Fri, 17 Apr 2009 14:58:28 +0100
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 17 Apr 2009 06:59:05 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 04/16/09 6:00 PM >>>
>How big NR_CPUS are we talking about? Is the overhead measurable, or is this
>a premature micro-optimisation?

We're shipping Xen in SLE11 with NR_CPUS=255, and I'm convinced we'll be asked to up this further in the service packs.

Also, micro-optimization reads for me like I was aiming at a performance issue, but the goal really just is to get the use of stack space down (and in particular, make it as independent as possible from configuration settings).

Jan

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] Re: next->vcpu_dirty_cpumask checking at the top of context_switch(), Jan Beulich <= [Xen-devel] Re: next->vcpu_dirty_cpumask checking at the top of context_switch(), Keir Fraser

Previous by Date:	Re: [Xen-devel] Second release candidate for Xen 3.4.0, wei zhou
Next by Date:	Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree, Jeremy Fitzhardinge
Previous by Thread:	[Xen-devel] [PATCH] ioemu: fix sdl mode, Cui, Dexuan
Next by Thread:	[Xen-devel] Re: next->vcpu_dirty_cpumask checking at the top of context_switch(), Keir Fraser
Indexes:	[Date] [Thread] [Top] [All Lists]