public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Adam Hunt <kinema@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O scheduler recomendation for Linux as a VMware guest
Date: Thu, 21 Oct 2004 10:31:29 +0200	[thread overview]
Message-ID: <20041021083126.GX10531@suse.de> (raw)
In-Reply-To: <b476569a0410201616415b0600@mail.gmail.com>

On Wed, Oct 20 2004, Adam Hunt wrote:
> I am forced to spend quite a bit of time with my only relatively
> powerful workstation booted into XP so I can do CAD work
> (unfortunately Autodesk's Inventor only runs on Windows).  Because of
> this unfortunate situation I am planning my first attempt to get the
> Linux install that I have on the other drive in this workstation to
> boot using VMware.  VMware has the ability to access raw disk
> partitions (as apposed to partitions stored in a file on a host
> partition) so I figure with some init and /etc magic I should be able
> to boot the system using VMware and when I am not drawing in Inventor
> I should be able to reboot and run Linux natively directly on the
> hardware.
> 
> What I am wondering is what I/O scheduler should I be using when the
> system is running within a VMware instance?  I figure that Windows
> will be scheduling the access to the physical hardware so I would
> assume that I want a bare bones priority based scheduler, something
> with the lowest possible overhead.  Is this correct?  If so, what
> would that scheduler be?

Probably deadline/cfq is the best fit, unless your host file is
perfectly laid out on disk in which case you can play with noop. As
Randy already pointed out, you can switch dynamically in the 2.6.9-bk
snapshots - so the best thing for you to do if you want to know for
sure, is to benchmark each of them for your workload. For most things
there should not be a noticable difference between cfq and deadline,
whether as makes a difference (for better or worse) is very work-load
dependent.

-- 
Jens Axboe


      parent reply	other threads:[~2004-10-21  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 23:16 I/O scheduler recomendation for Linux as a VMware guest Adam Hunt
2004-10-21  2:48 ` Randy.Dunlap
2004-10-21  8:31 ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041021083126.GX10531@suse.de \
    --to=axboe@suse.de \
    --cc=kinema@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox