Re: [Xen-devel] credit vs sedf scheduler

[Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>]

Hi, Markus

At first, did you see this thread?
http://lists.xensource.com/archives/html/xen-devel/2006-11/msg00198.html
Latest version of credit scheduler,
Runq is split to I/O intensive and CPU intensive.
(I/O have high priority.)

If your machine has just one I/O intensive jobs are exists,
It should be no problem.

Anyway, you should try latest xen-unstable at first. 

Thanks
Atsushi SAKAI



>Hi,
>i am using XEN on a voice mailbox system.
>One domU sends RTP datagrams every 20ms.
>Using the sedf scheduler it is easy to setup a domain which meets this
>criteria.
>
>I am disappointed by the announcement that sedf will be removed from future
>releases.
>Under credit the time slicing of 30ms and the fairness among the VCPU hurts
>my system.
>
>Multi core cpus and pinning each VCPU to a real CPU can solve this problem,
>but this will waste resources as real time apps/domUs normally are not CPU
>intensive.
>
>Why will sedf be removed from XEN?
>
>How will XEN support soft real-time needs in future?
>
>Was not the idea of having different schedulers the solution?
>
>regards,
>Markus

>_______________________________________________
>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