From: Christoph Hellwig <hch@caldera.de>
To: Mike Fedyk <mfedyk@matchmail.com>,
Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in the tree
Date: Tue, 26 Feb 2002 17:53:22 +0100 [thread overview]
Message-ID: <20020226175322.A31217@caldera.de> (raw)
In-Reply-To: <200202260135.18913.Dieter.Nuetzel@hamburg.de> <200202260707.g1Q77CJ02138@ns.caldera.de> <20020226162112.GF4393@matchmail.com>
In-Reply-To: <20020226162112.GF4393@matchmail.com>; from mfedyk@matchmail.com on Tue, Feb 26, 2002 at 08:21:12AM -0800
On Tue, Feb 26, 2002 at 08:21:12AM -0800, Mike Fedyk wrote:
> You should talk to Andrew Morton, as he plans to do this also.
Last time I talked to him he was primarily interested in the VM.
> I thought the internals of the scheduler weren't exposed to the rest of the
> kernel...
They shouldn't, But many old drivers do (and _had to_):
current->policy = SCHED_YIELD;
schedule();
which isn't possible with the new scheduler.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2002-02-26 16:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:35 2.4.19-preX: What we really need: -AA patches finally in the tree Dieter Nützel
2002-02-26 1:02 ` Ken Brownfield
2002-02-26 1:13 ` Andrew Morton
2002-02-26 7:20 ` Jens Axboe
2002-02-26 1:39 ` Alan Cox
2002-02-26 1:15 ` Shawn Starr
2002-02-26 1:32 ` Martin J. Bligh
2002-02-24 5:44 ` Daniel Phillips
2002-02-26 4:33 ` Martin J. Bligh
2002-02-26 11:42 ` Rik van Riel
2002-02-26 1:40 ` Rik van Riel
2002-02-26 1:49 ` Martin J. Bligh
2002-02-26 1:51 ` Alan Cox
2002-02-26 8:36 ` Christoph Rohland
2002-02-26 7:07 ` Christoph Hellwig
2002-02-26 16:21 ` Mike Fedyk
2002-02-26 16:53 ` Christoph Hellwig [this message]
2002-02-28 22:45 ` Bill Davidsen
2002-02-28 23:04 ` Rik van Riel
2002-03-01 1:04 ` 2.4.19-preX: What we really need: -AA patches finally in the Alan Cox
2002-03-01 1:14 ` Rik van Riel
2002-03-01 3:02 ` 2.4.19-preX: What we really need: -AA patches finally in the tree Bill Davidsen
2002-03-01 3:13 ` Rik van Riel
2002-03-01 3:43 ` Davide Libenzi
2002-03-01 10:36 ` Sean Hunter
2002-03-01 17:13 ` Davide Libenzi
2002-03-01 6:29 ` Olivier Galibert
2002-03-01 16:28 ` Dan Chen
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 6:41 dart
2002-03-05 21:49 ` Bill Davidsen
2002-03-06 1:05 ` Alan Cox
2002-03-06 1:45 ` James M.
2002-03-06 16:50 ` Ken Brownfield
2002-03-07 10:11 ` Leonid Mamtchenkov
2002-03-06 23:34 ` Yven Leist
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=20020226175322.A31217@caldera.de \
--to=hch@caldera.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.