From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Yuehai Xu <yuehaixu@gmail.com>
Cc: George.Dunlap@eu.citrix.com, xen-devel@lists.xensource.com,
yhxu@wayne.edu, Keir.Fraser@eu.citrix.com
Subject: Re: Question about the ability of credit scheduler to handle I/O and CPU intensive VMs
Date: Mon, 13 Sep 2010 16:29:31 -0700 [thread overview]
Message-ID: <4C8EB3DB.8060005@goop.org> (raw)
In-Reply-To: <AANLkTi=Ro24zg-yDPk1+=c0XsZSe2kNn8Gk07Bu4x0WN@mail.gmail.com>
On 09/13/2010 02:37 PM, Yuehai Xu wrote:
> The document http://www.xen.org/files/xensummit_intel09/George_Dunlap.pdf
> has explained why credit scheduler doesn't work well for CPU+I/O
> intensive workload, however, since nothing seems happened after this
> short paper, at least the performance of I/O remains poor. Is it
> because of some technical issues?
Have you tried the credit2 scheduler?
J
next prev parent reply other threads:[~2010-09-13 23:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 21:37 Question about the ability of credit scheduler to handle I/O and CPU intensive VMs Yuehai Xu
2010-09-13 23:29 ` Jeremy Fitzhardinge [this message]
2010-09-14 1:38 ` Yuehai Xu
[not found] ` <AANLkTin9E1m_jFcj4Ak7nB9OxcQynrznpQ_nNPi_U7hN@mail.gmail.com>
2010-09-14 14:58 ` Yuehai Xu
2010-09-30 12:28 ` Yuehai Xu
2010-09-30 13:27 ` George Dunlap
2010-10-05 2:52 ` Yuehai Xu
2010-10-05 14:16 ` George Dunlap
2010-10-05 14:56 ` Yuehai Xu
2010-10-05 15:02 ` George Dunlap
2010-10-07 22:18 ` Yuehai Xu
2010-10-08 0:25 ` Yuehai Xu
2010-10-08 9:57 ` George Dunlap
2010-10-08 10:03 ` George Dunlap
2010-10-08 10:11 ` George Dunlap
2010-10-10 4:08 ` Yuehai Xu
2010-10-10 8:30 ` cendhu
2010-10-11 11:05 ` George Dunlap
2010-10-12 12:42 ` Yuehai Xu
2010-10-18 10:25 ` George Dunlap
2010-10-05 4:30 ` question about lineat pagetable and mfn_x strongerwill
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=4C8EB3DB.8060005@goop.org \
--to=jeremy@goop.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yhxu@wayne.edu \
--cc=yuehaixu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.