public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Hunt <kinema@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: I/O scheduler recomendation for Linux as a VMware guest
Date: Wed, 20 Oct 2004 11:16:05 -1200	[thread overview]
Message-ID: <b476569a0410201616415b0600@mail.gmail.com> (raw)

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?

IIRC someone (Ingo?) was working on the ability to change schedules
during runtime.  How has that work progressed?  Is it available in any
kernel trees?

--adam

             reply	other threads:[~2004-10-20 23:43 UTC|newest]

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

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=b476569a0410201616415b0600@mail.gmail.com \
    --to=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