From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Weekes Subject: Re: Disk IO scheduling in XEN Date: Thu, 24 Mar 2011 13:25:37 -0700 Message-ID: <4D8BA8C1.8040503@nuclearfallout.net> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0071456259==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Paresh Nakhe , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0071456259== Content-Type: multipart/alternative; boundary="------------010402070703000305050007" This is a multi-part message in MIME format. --------------010402070703000305050007 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 3/24/2011 1: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? Ian Campbell forward-ported the 2.6.18-xen.hg patches for this but I don't think that they've been merged into the main git 2.6.32 stable tree yet. Check the list archives for the subject line "unfair servicing of DomU vbd requests" for more information on this. > Which one would be better first come first serve or round robin and why? Of the two, RR, because domains can become starved otherwise. -John --------------010402070703000305050007 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 3/24/2011 1: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?

Ian Campbell forward-ported the 2.6.18-xen.hg patches for this but I don't think that they've been merged into the main git 2.6.32 stable tree yet. Check the list archives for the subject line "unfair servicing of DomU vbd requests" for more information on this.

Which one would be better first come first serve or round robin and why?

Of the two, RR, because domains can become starved otherwise.

-John
--------------010402070703000305050007-- --===============0071456259== 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 --===============0071456259==--