[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen 3.0.3 disk i/o

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Brian Hays" <brian.hays@xxxxxxxxx>
  • Date: Mon, 9 Oct 2006 14:10:24 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 09 Oct 2006 11:10:53 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=J/WlN35k0jc1doZY75rUzutCUFYVzHNtqngEr+OmZNepHNJj7qmPcEowvKUq/LP58P3ykTCsmEmaOJqcgXUA48AMDGge5p9hcxP1BkORsJEnHVD6s4NyWJCQr1Tk907K3Fv1fCPFWSZ5jihfhbRulyOZYNkcYBDSSUe1EW5zanE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi Keir,

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]"

Thank you,

On 10/9/06, Keir Fraser < Keir.Fraser@xxxxxxxxxxxx> wrote:
On 9/10/06 5:30 am, "Brian Hays" < brian.hays@xxxxxxxxx> wrote:

I've seen from time to time where a domU using heavy disk I/O can slow down an entire server (including all other domU's and dom0). Is there a way to schedule or limit this in Xen 3.0.3?

You should be able to use the CFQ I/O scheduler in domain0 to set per-domain scheduling parameters.

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.