[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] credit vs sedf scheduler


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Markus Kremer" <markus314@xxxxxxxxxxxxxx>
  • Date: Thu, 16 Nov 2006 09:13:39 +0100
  • Delivery-date: Thu, 16 Nov 2006 00:13:48 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Hi0W1S4LFrBjH50Pk76AMsSRBCkucHtl3r0gj0qBxSL8N6ac8d/Rqofffq06xkf3D50tBhbYnyn/FMesdlMaCCXMo7qDrGOsLscbs1PvH366T9HyvRiYUO7YVG8D5CDLMvWmHvqqFKkpEwcep3Kvdj2f7JDIZUBzdkHjFc/bHCw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.