search for: ratelimit_us

...prv->credits_per_tslice = CSCHED_CREDITS_PER_MSEC * prv->tslice_ms; +} + static int csched_sys_cntl(const struct scheduler *ops, struct xen_sysctl_scheduler_op *sc) @@ -1089,7 +1100,7 @@ csched_sys_cntl(const struct scheduler *ops, || params->ratelimit_us < XEN_SYSCTL_SCHED_RATELIMIT_MIN)) || MICROSECS(params->ratelimit_us) > MILLISECS(params->tslice_ms) ) goto out; - prv->tslice_ms = params->tslice_ms; + __csched_set_tslice(prv, params->tslice_ms); prv->ratelimit_us = para...

...s 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_TICKS_PER_TSLICE; if ( prv->tslice_ms < prv->ticks_per_tslice ) prv->ticks_per_tslice = 1; prv->tick_period_us = prv->tslice_ms...

...> 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 2012 +0000...

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

...: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":[],"cmdline":"root=/dev/...