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

[Gareth S Bestor <bestorga@xxxxxxxxxx>]

I agree. Certainly Xen currently exposes the ability to accomplish this, its just not perhaps in our absolute most preferred convenient form; ie !X(y) forall y --> !X(y1) && !X(y2)... :-)

This is a classic example of a meaningful value-add that a (CIM) mgmt app can expose on top of the raw functionality provided by Xen!

- Gareth

Dr. Gareth S. Bestor
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186

"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>

"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>

12/19/06 07:24 AM

To	"Keir Fraser" <keir@xxxxxxxxxxxxx>, "Emmanuel Ackaouy" <ackaouy@xxxxxxxxx>
cc	<xen-cim@xxxxxxxxxxxxxxxxxxx>, "Jim Fehlig" <jfehlig@xxxxxxxxxx>, Gareth S Bestor/Beaverton/IBM@IBMUS
Subject	RE: Removing pcpus from the scheduling pool

Keir,
> >> * 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.
Thanks.
That should solve it.

Raj

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