WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Disk IO scheduling in XEN

To: "Paresh Nakhe" <paresh.nakhe@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Disk IO scheduling in XEN
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 25 Mar 2011 09:29:53 +1100
Cc:
Delivery-date: Thu, 24 Mar 2011 15:30:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinHMeu5S_yes-Ut8zx=L==DaqZmmejAZnb4TbGM@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinHMeu5S_yes-Ut8zx=L==DaqZmmejAZnb4TbGM@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvqYPjCjVl9qxf3Q8eaDu4mz7KlTQAEd6vg
Thread-topic: [Xen-devel] Disk IO scheduling in XEN
> 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?
> 
> Which one would be better first come first serve or round robin and
why?
> 

There was a discussion about this recently. It turns out that one DomU
can starve the others and there are real life examples of this
happening. Patches have been proposed and posted but I don't know into
what trees.

James

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

<Prev in Thread] Current Thread [Next in Thread>