masami.watanabe@jp.fujitsu.com
2006-Aug-17 10:37 UTC
[Xen-devel] [PATCH]configuration files(sched-credit)
Currently with the credit scheduler, cpu_weight cannot be assigned to guest
domains at boot time.(it can be set with xm sched-weight after booting)
This patch allows CPU weight, and CAP to be set by the Xen configuration
files.
Specification:
The following can be added to the Xen configuration files.
1.CPU WEIGHT [OPTIONAL]
cpu_weight = cpu weight value
-sets the cpu time ratio to be allocated to the domain
-the scale and the default value may vary according to the scheduler used.
No modification has been made for the bvt scheduler.
--credit scheduler: 1~65535 (default:256)
--bvt scheduler: float value (default:1.0)
2.CAP [OPTIONAL]
cpu_cap= value
-this is only valid when using the credit scheduler
-allots the maximum CPU usage percentage for the domain
-the domain will use
-- (value x 0.01) physical CPUs
ex: 50 for 0.5 physical CPU
100 for 1.0 physical CPU
400 for 4.0 physical CPU
-- default:0.0 (no limit)
Improvements:
- allows cpu_cap to be set in the Xen configuration files
- sets default cpu_cap and cpu_weight values for each scheduler
- passes the cpu_cap and the cpu_weight in the Xen configuration files
to xend
Modifications:
-To allow cpu_cap to be set in the Xen configuration files
python/xen/xm/create.py, python/xen/xend/XendDomainInfo.py,
python/xen/lowlevel/xc/xc.c
-To allow cpu_cap and cpu_weight in the Xen configuration files to be
passed to xend
python/xen/sv/CreateDomain.py, libxc/xenctrl.h, xc_domain.c,
python/xen/lowlevel/xc/xc.c
-To set default values for each scheduler
Previously, the default value, 1.0 had been set for the bvt scheduler by
the Xen configuration files parsing in XendDomainInfo.py. It has now been
modified so that default values are set in xc_domain.c after the scheduler
type has been determined.
In XendDomainInfo.py, the default value is now set to -1
libxc/xc_domain.c
Signed-off-by: Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Watanabe
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Masami Watanabe
2006-Sep-22 02:42 UTC
Re: [Xen-devel] [PATCH]configuration files(sched-credit)
Hi, Do you have any comment? If you have no comment, could you commit this patch? http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html On Thu, 17 Aug 2006 19:37:03 +0900, Masami Watanabe wrote:> Currently with the credit scheduler, cpu_weight cannot be assigned to guest > domains at boot time.(it can be set with xm sched-weight after booting) > This patch allows CPU weight, and CAP to be set by the Xen configuration > files. > > > Specification: > The following can be added to the Xen configuration files. > > 1.CPU WEIGHT [OPTIONAL] > cpu_weight = cpu weight value > > -sets the cpu time ratio to be allocated to the domain > -the scale and the default value may vary according to the scheduler used. > No modification has been made for the bvt scheduler. > --credit scheduler: 1~65535 (default:256) > --bvt scheduler: float value (default:1.0) > > 2.CAP [OPTIONAL] > cpu_cap= value > > -this is only valid when using the credit scheduler > -allots the maximum CPU usage percentage for the domain > -the domain will use > -- (value x 0.01) physical CPUs > ex: 50 for 0.5 physical CPU > 100 for 1.0 physical CPU > 400 for 4.0 physical CPU > -- default:0.0 (no limit) > > Improvements: > - allows cpu_cap to be set in the Xen configuration files > - sets default cpu_cap and cpu_weight values for each scheduler > - passes the cpu_cap and the cpu_weight in the Xen configuration files > to xend > > Modifications: > -To allow cpu_cap to be set in the Xen configuration files > python/xen/xm/create.py, python/xen/xend/XendDomainInfo.py, > python/xen/lowlevel/xc/xc.c > -To allow cpu_cap and cpu_weight in the Xen configuration files to be > passed to xend > python/xen/sv/CreateDomain.py, libxc/xenctrl.h, xc_domain.c, > python/xen/lowlevel/xc/xc.c > -To set default values for each scheduler > Previously, the default value, 1.0 had been set for the bvt scheduler by > the Xen configuration files parsing in XendDomainInfo.py. It has now been > modified so that default values are set in xc_domain.c after the scheduler > type has been determined. > In XendDomainInfo.py, the default value is now set to -1 > libxc/xc_domain.c > > > Signed-off-by: Masami Watanabe <masami.watanabe@jp.fujitsu.com> > > Watanabe_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alastair Tse
2006-Sep-22 11:20 UTC
Re: [Xen-devel] [PATCH]configuration files(sched-credit)
On Fri, 2006-09-22 at 11:42 +0900, Masami Watanabe wrote:> Hi, > > Do you have any comment? > If you have no comment, could you commit this patch? > > http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.htmlThe patch does not apply to xen-unstable. Since changeset 11241, the xc_domain_setcpuweight is a no-op. Instead you should probably use xc.sched_credit_domain_set directly from XendDomain.py and leave libxc''s domain_setcpuweight alone. Cheers, Alastair _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Masami Watanabe
2006-Sep-24 19:17 UTC
Re: [Xen-devel] [PATCH]configuration files(sched-credit)
Thanks Alastair,
This is take 2 on configuration files(sched-credit).
The specification is as mentioned at
http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html
The difference is follows.
- change default value in XendDomainInfo.py
- xc_domain_setcpuweight was not used
- xc.sched_credit_domain_set was used directly from XendDomain.py.
domain_create and domain_sched_credit_set@XendDomain.py
-> xc.sched_credit_domain_set
Signed-off-by: Masami Watanabe <masami.watanabe@jp.fujitsu.com>
On Fri, 22 Sep 2006 12:20:33 +0100, Alastair Tse wrote:> On Fri, 2006-09-22 at 11:42 +0900, Masami Watanabe wrote:
> > Hi,
> >
> > Do you have any comment?
> > If you have no comment, could you commit this patch?
> >
> >
http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html
>
> The patch does not apply to xen-unstable. Since changeset 11241, the
> xc_domain_setcpuweight is a no-op. Instead you should probably use
> xc.sched_credit_domain_set directly from XendDomain.py and leave
libxc''s
> domain_setcpuweight alone.
>
> Cheers,
>
> Alastair
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Masami Watanabe
2006-Oct-22 10:55 UTC
[Xen-devel] [PATCH]configuration files(sched-credit)
Hi, Do you have any comment? If you have no comment, could you commit this patch? http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html This is take 3 on configuration files(sched-credit). This patch matched to CS11853. Signed-off-by: Masami Watanabe <masami.watanabe@jp.fujitsu.com> Best regards, Masami On Mon, 25 Sep 2006 04:17:35 +0900, Masami Watanabe wrote:> Thanks Alastair, > > This is take 2 on configuration files(sched-credit). > > The specification is as mentioned at > http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html > > The difference is follows. > - change default value in XendDomainInfo.py > - xc_domain_setcpuweight was not used > - xc.sched_credit_domain_set was used directly from XendDomain.py. > domain_create and domain_sched_credit_set@XendDomain.py > -> xc.sched_credit_domain_set > > > Signed-off-by: Masami Watanabe <masami.watanabe@jp.fujitsu.com> > > > On Fri, 22 Sep 2006 12:20:33 +0100, Alastair Tse wrote: > > On Fri, 2006-09-22 at 11:42 +0900, Masami Watanabe wrote: > > > Hi, > > > > > > Do you have any comment? > > > If you have no comment, could you commit this patch? > > > > > > http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00999.html > > > > The patch does not apply to xen-unstable. Since changeset 11241, the > > xc_domain_setcpuweight is a no-op. Instead you should probably use > > xc.sched_credit_domain_set directly from XendDomain.py and leave libxc''s > > domain_setcpuweight alone. > > > > Cheers, > > > > Alastair > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel