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

[Xen-devel] About the credit2 scheduler


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jia Rao <rickenrao@xxxxxxxxx>
  • Date: Tue, 16 Feb 2010 14:23:39 -0500
  • Delivery-date: Tue, 16 Feb 2010 11:24:35 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pKKLaFAcHXOGQy79Y/pMBL+bJ107LRmxP/ckXNFNFFuY6vFj6bLgUHxckO0MnkbZCU D4nXEysICLub3J3hf9y/eN/b3tmvXvfNsiFpoUeNBkVeCEWEdXJV4OSE0YoV4LtTGeHj Dp4++7ZFHx+17ZIr4Xe43rUKEqsFdXcBRurxA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,

I am curious that how is the credit scheduler compared to the linux default CPU scheduler ?
They look quite similar. Do the problems in the credit scheduler also exist in Linux CPU scheduler?

What I understand is that, virtual machine monitors have a higher requirement in "fair sharing" than Linux. Therefore, we need credit-based scheduling which can possibly cause problems for latency sensitive workloads.

Thanks 
_______________________________________________
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®.