Re: [Xen-devel] [PATCH] tunable time slice for credit scheduler - Keir Fraser - com.xensource.lists.xen-devel

6 messages in com.xensource.lists.xen-develRe: [Xen-devel] [PATCH] tunable time ...

From	Sent On	Attachments
Atsushi SAKAI	17 May 2007 01:24	.patch
tgh	17 May 2007 01:53
Emmanuel Ackaouy	27 Jun 2007 05:08
Keir Fraser	27 Jun 2007 05:26
Atsushi SAKAI	27 Jun 2007 21:51
Mark Williamson	30 Aug 2007 20:35

Subject:	Re: [Xen-devel] [PATCH] tunable time slice for credit scheduler
From:	Keir Fraser (ke...@xensource.com)
Date:	06/27/2007 05:26:16 AM
List:	com.xensource.lists.xen-devel

I'm not sure that extra parameters are what the scheduler really needs. Tuning for better performance 'out of the box' would be more useful. Under what circumstances were you seeing VNC connection timeouts? If it's an extreme overload situation then that can likely be detected and dealt with by automatic time-slice adjustment. I can't see a time-slice option being used sensibly in many scenarios.

-- Keir

On 27/6/07 13:08, "Emmanuel Ackaouy" <acka...@gmail.com> wrote:

The sched_credit.c part of this patch looks good to me (except for the coding style issues). Before adding per-domain tunable time slices though, shouldn't we make the global time slice tunable?

On May 17, 2007, at 10:25, Atsushi SAKAI wrote:

Hi,

This patch intends to add tunablity for time slice on credit scheduler. Each domain can change time slice.

for example, xm sched-credit -d 0 -s 20 (unit is msec)

Signed-off-by: Atsushi SAKAI <sak...@jp.fujitsu.com>

c.f. 1)libxc(pyxc) forgets help message for cap. I add it on tools/python/xen/lowlevel/xc/xc.c

2)time slice can set from 1 to 100(msec). I have see VNC connection timeout problem for many domain on one CPU. For this reason, it can set time slice from 1 to 100 msec. Of course, default value is 30msec.

<tune_timeslice.patch>_______________________________________________ Xen-devel mailing list Xen-...@lists.xensource.com http://lists.xensource.com/xen-devel