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] RFC: large system support - 128 CPUs

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: large system support - 128 CPUs
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 13 Aug 2008 09:26:26 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Bill Burns <bburns@xxxxxxxxxx>
Delivery-date: Wed, 13 Aug 2008 01:27:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080813082256.GF27463@xxxxxxxxxxxxxxxxxxxxx>
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
Thread-index: Acj9HkbghXx6NGkREd2S1gAX8io7RQ==
Thread-topic: [Xen-devel] RFC: large system support - 128 CPUs
User-agent: Microsoft-Entourage/11.4.0.080122
On 13/8/08 09:22, "Tim Deegan" <Tim.Deegan@xxxxxxxxxx> wrote:

> At 09:21 +0100 on 13 Aug (1218619274), Jan Beulich wrote:
>> Both seem to be hacks to get to 128 CPUs, without consideration of how
>> to go beyond that
> 
> I think the shadow_page_info one is a general fix for my implicit
> assumption that sizeof(cpumask_t) == sizeof (long).

Do some fields after the cpumask need to line up in both structures? Placing
a dummy cpumask in the shadow_page structure might make most sense.

For the other one I'll have to think a bit. The need for GDT entries per CPU
currently obviously means scaling much past a few hundred CPUs is going to
be difficult.

 -- Keir



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