From: Brandon Low <lostlogic@lostlogicx.com>
To: Andreas Tscharner <starfire@dplanet.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New scheduler in 2.4. series?
Date: Mon, 4 Feb 2002 16:35:13 -0600 [thread overview]
Message-ID: <20020204163513.A31041@lostlogicx.com> (raw)
In-Reply-To: <20020204231938.18755478.starfire@dplanet.ch>
In-Reply-To: <20020204231938.18755478.starfire@dplanet.ch>; from starfire@dplanet.ch on Mon, Feb 04, 2002 at 11:19:38PM +0100
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Seeing the new scheduler in 2.4 would be nice! However, soon wouldn't be nice, because there are a lot of 3rd party kernel
modules that try to make calls against the old scheduler that don't seem to work. My personal case in point is Bestcrypt
( www.jetico.sci.fi ). Just my thoughts on the matter.
--Brandon
-=-=-=-=-=-=-=-Previous Message(s)-=-=-=-=-=-=-=-
> Hello World,
> Hello Marcelo,
>
> Is there any chance, that the new scheduler will be in the 2.4 series soon?
>
> Regards
> Andreas
> --
> Andreas Tscharner starfire@dplanet.ch
> -------------------------------------------------------------------------
> "Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning." -- Rich Cook
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-04 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 22:19 New scheduler in 2.4. series? Andreas Tscharner
2002-02-04 22:35 ` Brandon Low [this message]
2002-02-05 18:38 ` Kristian
2002-02-05 23:06 ` Ingo Molnar
2002-02-05 21:22 ` Kristian
2002-02-05 23:26 ` Ingo Molnar
2002-02-05 21:53 ` Kristian
2002-02-06 8:08 ` Kristian
2002-02-06 13:00 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 0:02 Dieter Nützel
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=20020204163513.A31041@lostlogicx.com \
--to=lostlogic@lostlogicx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=starfire@dplanet.ch \
/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