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-cim

[Xen-cim] Re: Removing pcpus from the scheduling pool

To: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
Subject: [Xen-cim] Re: Removing pcpus from the scheduling pool
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 19 Dec 2006 15:14:28 +0000
Cc: xen-cim@xxxxxxxxxxxxxxxxxxx, Jim Fehlig <jfehlig@xxxxxxxxxx>
Delivery-date: Thu, 28 Dec 2006 03:05:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <94C8C9E8B25F564F95185BDA64AB05F604853661@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccjXn4R5ruqZzR9Qr6ddPxBJlz8mgAHnBMgAADcdQ8=
Thread-topic: Removing pcpus from the scheduling pool
User-agent: Microsoft-Entourage/11.2.5.060620
On 19/12/06 15:01, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx> wrote:

>> * Support for ResourcePoolConfigurationService on some pool types,
>> e.g. ProcessorPool.This functionality will support for example
>> removing PCPUs from the pool and dedicate to management domain, thus
>> restricting set of PCPUs available for consumption by VMs.  Does xen
> support 
>> this?  Can we mask PCPUs such that they are not available to VMs?
> End quote.
> 
> What needs to be done to add this functionality to the current
> scheduler? 

The scheduler supports this already: it will simply be necessary to remove
the PCPUs removed from the pool from every domain's affinity map. All this
requires is for the tool stack on the box to remember which PCPUS are in the
pool and apply that as a mask to the affinity map of every guest.

 -- Keir


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

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