| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented
|
To: |
Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented |
|
From: |
Ryan Harper <ryanh@xxxxxxxxxx> |
|
Date: |
Tue, 9 May 2006 10:44:45 -0500 |
|
Cc: |
Xen-devel@xxxxxxxxxxxxxxxxxxx, "Krysan, Susan" <KRYSANS@xxxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx> |
|
Delivery-date: |
Tue, 09 May 2006 08:45:12 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<A95E2296287EAD4EB592B5DEEFCE0E9D4BA63B@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<A95E2296287EAD4EB592B5DEEFCE0E9D4BA63B@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.6+20040907i |
* Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> [2006-05-09 10:07]:
> > The comments for dom0-cpus in the xend-config.sxp file
> > indicate that setting this value to 0 in an SMP system will
> > cause dom0 to use all the available CPUs. However, it appears
> > as if setting this value to 0 does not change the number of
> > CPUs at all.
> >
> > I'm running SLES10 Beta 11 and xen-unstable changeset 9960 on
> > a Unisys ES7000 with 32 CPUs and 32GB memory. In
> > xend-config.sxp, dom0-cpus is set to 0. When xen dom0 boots,
> > it is using all 32 procs (as reported by 'grep processor
> > /proc/cpuinfo | wc -l').
> >
> > If I edit the xend-config.sxp file, change the value of
> > dom0-cpus to 1, and restart xend, dom0 correctly uses 1 CPUs.
> > If I then change dom0-cpus to 0 and restart xend, dom0 still
> > uses 1 cpu. The only way to have dom0 use 32 cpus again is to
> > either set the value of dom0-cpus to 32, or reboot xen.
> >
> > Has anyone else seen this behavior?
>
> You can just use the normal xm commands to vary the number of CPUs.
> Restarting xend is a rather brutal way of trying to achieve the same
> thing...
Is it worth keeping dom0-cpus then?
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@xxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home