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

Re: [Xen-users] io scheduler


  • To: mogensv@xxxxxxxxxxxxxxxx
  • From: Anand <xen.mails@xxxxxxxxx>
  • Date: Tue, 10 Jan 2006 16:58:57 +0530
  • Cc: Xen Users <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 10 Jan 2006 11:35:21 +0000
  • 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=UBqBF09v3Blu10CtQRLIsiz9K8uQs6HiIq/Zud8OhhdSPFQ09HFeVbkB4iW7J1yyDjmfbiJFdF30oh0GiCGYWaIB6HKKRn0qOnC3Y/I8CE/XPEBhY45S9O7Pf1sAgJKTseYYCaeuGrBRcjIECBU6Y3OpfPLmwOy9UT6+1p5nyag=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 1/10/06, Mogens Valentin <mogensv@xxxxxxxxxxxxxxxx> wrote:
On non-xen, yes. There's some benchmarks somewhere (don't seem to find
them right now) about advanteges of the various ones.
/usr/src/linux/Documentation/kernel-parameters.txt  says a few words.

From the above kernel-parameters.txt

        elevator=       [IOSCHED]
                        Format: {"as"|"cfq"|"deadline"|"noop"}
                        See Documentation/block/as- iosched.txt
                        and Documentation/block/deadline-iosched.txt for details.

I tried to pass elevator=cfq on the dom0, it worked out. On domU however i am passing the same parameter and the scheduler is still noop.

-bash-3.00# cat /sys/block/sda1/queue/scheduler
[noop] anticipatory deadline cfq

Any ideas why its using 2 different schedulers ?

--

regards,

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

 


Rackspace

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