xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params

from [Masaki Kanno]

[Permanent Link][Original]

To:	Jim Fehlig <jfehlig@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params
From:	Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date:	Wed, 06 Jun 2007 20:20:44 +0900
Delivery-date:	Wed, 06 Jun 2007 04:19:16 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<46660BFC.8040908@xxxxxxxxxx>
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:	<46660BFC.8040908@xxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hi Jim,

If the patch is applied, I think that "cpu_weight" and "cpu_cap" 
disappear from information of xm list.  Is my thought right? 

Best regards,
 Kan

>When creating domains that specify scheduler parameters with XenAPI, the
>specified parameters are not used when starting the domain.  As an
>example, here is a snippet of internal config for a domain created via
>XenAPI that contains scheduling params:
>
>(domain
>    (domid 6)
>    (vcpus_params ((cap 100) (weight 512)))
>    ...
>    (cpu_weight 256)
>    (cpu_cap 0)
>    ...
>)
>
>Starting the domain results in following scheduler settings:
>
>jfehlig4:/home/jfehlig/cim/cimxml # xm sched-credit -d sles10_nographic
>Name                              ID Weight Cap
>sles10_nographic                   6    256    0
>
>The attached patch collapses cpu_weight and cpu_cap in XendConfig into
>the vcpus_params dictionary.  The patch has been tested using xm and
>XenAPI on config with and without scheduler parameters.
>
>Regards,
>Jim
>
>Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxxxx>
>
>
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel


_______________________________________________
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] [PATCH][xend] Fix handling of scheduler params, Jim Fehlig Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params, Masaki Kanno <= Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params, Jim Fehlig Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params, Masaki Kanno

Previous by Date:	Re: [Xen-devel] error compiling xen, pradeep singh rautela
Next by Date:	Re: [Xen-devel] [patch 14/33] xen: xen time implementation, Keir Fraser
Previous by Thread:	[Xen-devel] [PATCH][xend] Fix handling of scheduler params, Jim Fehlig
Next by Thread:	Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params, Jim Fehlig
Indexes:	[Date] [Thread] [Top] [All Lists]