From: Christoph Hellwig <hch@ns.caldera.de>
To: Khalid Aziz <khalid@fc.hp.com>
Cc: Hubertus Franke <frankeh@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Mike Kravetz <mkravetz@sequent.com>,
Fabio Riccardi <fabio@chromium.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: a quest for a better scheduler
Date: Wed, 4 Apr 2001 17:55:44 +0200 [thread overview]
Message-ID: <20010404175544.A6240@caldera.de> (raw)
In-Reply-To: <OF401BD38B.CF3B1E9F-ON85256A24.0048543A@pok.ibm.com> <3ACB4156.160B7937@fc.hp.com>
In-Reply-To: <3ACB4156.160B7937@fc.hp.com>; from khalid@fc.hp.com on Wed, Apr 04, 2001 at 09:44:22AM -0600
On Wed, Apr 04, 2001 at 09:44:22AM -0600, Khalid Aziz wrote:
> Let me stress that HP scheduler is not meant to be a replacement for the
> current scheduler. The HP scheduler patch allows the current scheduler
> to be replaced by another scheduler by loading a module in special
> cases.
HP also has a simple mq patch that is _not_ integrated into the pluggable
scheduler framework, I have used it myself.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-04-04 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 13:43 a quest for a better scheduler Hubertus Franke
2001-04-04 13:25 ` Ingo Molnar
2001-04-04 13:34 ` Ingo Molnar
2001-04-04 15:08 ` Andrea Arcangeli
2001-04-04 16:50 ` [Lse-tech] " Kanoj Sarcar
2001-04-04 17:16 ` Andrea Arcangeli
2001-04-04 17:49 ` Kanoj Sarcar
2001-04-04 18:00 ` Andrea Arcangeli
2001-04-05 11:13 ` Zdenek Kabelac
2001-04-04 16:39 ` Kanoj Sarcar
2001-04-04 17:00 ` Andrea Arcangeli
2001-04-04 15:44 ` Khalid Aziz
2001-04-04 15:55 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-04 17:03 [Lse-tech] " Hubertus Franke
2001-04-04 17:14 ` Kanoj Sarcar
2001-04-04 17:34 Hubertus Franke
2001-04-04 17:40 Paul McKenney
2001-04-05 11:14 alad
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=20010404175544.A6240@caldera.de \
--to=hch@ns.caldera.de \
--cc=fabio@chromium.com \
--cc=frankeh@us.ibm.com \
--cc=khalid@fc.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=mkravetz@sequent.com \
/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