From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paresh Nakhe <paresh.nakhe@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Disk IO scheduling in XEN
Date: Fri, 25 Mar 2011 14:48:46 +0000 [thread overview]
Message-ID: <4D8CAB4E.90704@goop.org> (raw)
In-Reply-To: <AANLkTinHMeu5S_yes-Ut8zx=L==DaqZmmejAZnb4TbGM@mail.gmail.com>
On 03/24/2011 08:19 PM, Paresh Nakhe wrote:
> Hi,
>
> We are working on a project to modify the disk scheduling mechanism in
> XEN a bit in an attempt to improve it. In the paper "Xen and the Art
> of Virtualization" following is mentioned.
>
> /"Xen services batches of requests from competing domains in a
> simple round-robin fashion; these are then passed to a standard elevator
> scheduler before reaching the disk hardware/"
>
> We were going through linux-jeremy source code in an attempt to map
> the above in code. We could not however do so. On the contrary we came
> to the conclusion that there is no such mechanism. Domain 0 services
> requests as soon as it receives a hypercall from a guest domain. Are
> we right?
There's no explicit Xen-specific disk scheduling. Linux has a great
deal of intrinsic mechanisms for setting up disk scheduling, including
using cgroups to schedule groups of processes, so you can use those to
get any particular scheduling policy you desire.
> Which one would be better first come first serve or round robin and why?
I think there are many more options for disk scheduling than those.
For example: "is it better for guests to schedule their own requests, or
should they just pass requests straight through?".
J
prev parent reply other threads:[~2011-03-25 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 20:19 Disk IO scheduling in XEN Paresh Nakhe
2011-03-24 20:25 ` John Weekes
2011-03-24 22:29 ` James Harper
2011-03-25 9:58 ` Ian Campbell
2011-03-25 14:48 ` Jeremy Fitzhardinge [this message]
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=4D8CAB4E.90704@goop.org \
--to=jeremy@goop.org \
--cc=paresh.nakhe@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 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.