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

[Xen-users] io scheduler


  • To: Xen Users <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Anand <xen.mails@xxxxxxxxx>
  • Date: Mon, 9 Jan 2006 16:15:22 +0530
  • Delivery-date: Mon, 09 Jan 2006 10:51:40 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=HHhmG+sUK98CAiUqZHFk2Dt6XrhQDJDZhaDtJAwqL5R+GFDUmWyHRX2sQi57dI3p7vJ1XqRZD6UMNkUkrcrNR0uXDa8aG32GYzWO6SQLH8cJb7oWDpAdVWJKNtNbHewyYwXvVrSSsVYkrTIKs4I+XioMZlfETE9+6Cw/7rst5NA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Looking in the dmesg for a domU, i saw the following:

io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered

Reading docs i found it was about the Linux IO Scheduler.

cat /sys/block/sda1/queue/scheduler

[noop] anticipatory deadline cfq

Now using cfq for scheduler

echo cfq > /sys/block/sda1/queue/scheduler

cat /sys/block/sda1/queue/scheduler

noop anticipatory deadline [cfq]

Now there is  a log entry in /var/log/messages about cfq, it says

Jan  9 05:39:28 host6 kernel: cfq: depth 4 reached, tagging now on

The same message is also displayed on the console of domU.

The scheduler docs say that using elevator= option with kernel a scheduler can be specified at the command line, however if i try to do that in domU, it doesn't work.

My dom0 has anticipatory as the scheduler which is the default IO scheduler.

Any one has any ideas or worked with the io scheduler ?
--

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®.