From: Jia Rao <rickenrao@gmail.com>
To: xen-devel@lists.xensource.com
Subject: About the credit2 scheduler
Date: Tue, 16 Feb 2010 14:23:39 -0500 [thread overview]
Message-ID: <994429491002161123u4282ftb407f1d700fac36b@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 428 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 526 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-02-16 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 19:23 Jia Rao [this message]
2010-02-17 12:14 ` About the credit2 scheduler George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=994429491002161123u4282ftb407f1d700fac36b@mail.gmail.com \
--to=rickenrao@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).