search for: tslice_m

.../sched_credit.c old mode 100644 new mode 100755 index 28dafcf..db5512e --- a/xen/common/sched_credit.c +++ b/xen/common/sched_credit.c @@ -1071,6 +1071,17 @@ csched_dom_cntl( return 0; } +static inline void +__csched_set_tslice(struct csched_private *prv, unsigned timeslice) +{ + prv->tslice_ms = timeslice; + prv->ticks_per_tslice = CSCHED_TICKS_PER_TSLICE; + if ( prv->tslice_ms < prv->ticks_per_tslice ) + prv->ticks_per_tslice = 1; + prv->tick_period_us = prv->tslice_ms * 1000 / prv->ticks_per_tslice; + prv->credits_per_tslice = CSCHED_CREDI...

...e slice to be *greater* than 30ms, the VM gets much *less* CPU cycles than its allocation -when setting the time slice to be *smaller* than 30ms, the VM gets much *more* CPU cycles than its allocation Problem happens in sched_credit.c/csched_sys_cntl(): -------------------- after changing prv->tslice_ms, other parameters *should* also be changed accordingly: csched_sys_cntl() { ... prv->tslice_ms = params->tslice_ms; prv->ratelimit_us = params->ratelimit_us; ------- /* my patch: these parameters should also be changed */ prv->ticks_per_tslice = CSCHED_TICK...

Add a xen command-line parameter, sched_credit_tslice_ms, to set the timeslice of the credit1 scheduler. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff -r 4a4882df5649 -r 782284c5b1bc xen/common/sched_credit.c --- a/xen/common/sched_credit.c Wed Aug 31 15:23:49 2011 +0100 +++ b/xen/common/sched_credit.c Thu Sep 01 16:29:50 2011...

...@eu.citrix.com> Committed-by: Keir Fraser <keir@xen.org> changeset: 24880:dd9e8f1ebed1 user: George Dunlap <george.dunlap@eu.citrix.com> date: Thu Feb 23 10:17:21 2012 +0000 scheduler: Implement SCHEDOP sysctl for credit scheduler Allow tslice_ms and ratelimit_us to be modified. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Committed-by: Keir Fraser <keir@xen.org> changeset: 24879:c4bddb3422dd user: George Dunlap <george.dunlap@eu.citrix.com> date: Thu Feb 23 10:16:10 20...

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

...vice_model_version":null,"device_model_stubdomain":"<default>","device_model":null,"device_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params":{"weight":0,"cap":0,"tslice_ms":0,"ratelimit_us":0,"period":0,"slice":0,"latency":0,"extratime":0},"u":{"kernel":"/boot/vmlinuz-3.2.0-24-generic-pae","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cm...