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] Xen 3.0.3 disk i/o

To: "Brian Hays" <brian.hays@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Xen 3.0.3 disk i/o
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 9 Oct 2006 19:47:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Oct 2006 11:48:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e4ca66ec0610082130o59176675vd558370c05b2275e@xxxxxxxxxxxxxx><C14FB213.2374%Keir.Fraser@xxxxxxxxxxxx> <e4ca66ec0610091110p38014d42keaff24b99812b740@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbrznquv8jNLAU0T72HwVOLe7u94wABKuYQ
Thread-topic: [Xen-devel] Xen 3.0.3 disk i/o
> I'm using the kernel option "elevator=cfq" on both dom0 and domU's.
> However, the output of "cat /sys/block/sda1/queue/scheduler" within a
domU
> is still "[noop] anticipatory deadline cfq". Does this mean that cfq
is NOT
> being used even though the dmesg shows "io scheduler cfq registered
> (default)".
> 
> ...dom0 shows "noop anticipatory deadline [cfq]"

That means you're using cfq in dom0, which is what you want. Now you can
use 'ionice' to control scheduling from different domU block devices.

It doesn't matter what you use in domU, noop is fine.

Ian

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

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