From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jia Rao <rickenrao@gmail.com>
Subject: About the credit2 scheduler
Date: Tue, 16 Feb 2010 14:23:39 -0500
Message-ID: <994429491002161123u4282ftb407f1d700fac36b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0966957198=="
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

--===============0966957198==
Content-Type: multipart/alternative; boundary=000325557522ca5154047fbcab69

--000325557522ca5154047fbcab69
Content-Type: text/plain; charset=ISO-8859-1

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

--000325557522ca5154047fbcab69
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All,<div><br></div><div>I am curious that how is the credit scheduler co=
mpared to the linux default CPU scheduler ?</div><div>They look quite simil=
ar. Do the problems in the credit scheduler also exist in Linux CPU schedul=
er?</div>
<div><br></div><div>What I understand is that, virtual machine monitors hav=
e a higher requirement in &quot;fair sharing&quot; than Linux. Therefore, w=
e need credit-based scheduling which can possibly cause problems for latenc=
y sensitive workloads.</div>
<div><br></div><div>Thanks=A0</div>

--000325557522ca5154047fbcab69--


--===============0966957198==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

--===============0966957198==--