From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Cc: kpreempt-tech@lists.sourceforge.net, george@mvista.com
Subject: [PATCH] preemptive kernel
Date: 24 Jan 2002 04:39:00 -0500 [thread overview]
Message-ID: <1011865141.867.10.camel@phantasy> (raw)
The patch makes the Linux kernel preemptible: higher priority processes
can preempt other lower priority processes, even if they are running in
kernel-mode.
An updated preemptive kernel for 2.5.3-pre4 is available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.5/
And for 2.4.8-pre6 (and 2.4.18-pre6 + Ingo's O(1) Scheduler, J5):
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/
Most notably, the SMP instabilities under the new scheduler have been
solved. This version is rock-solid on my testing in both 2.4 and 2.5
under UP and SMP.
Ingo Molnar offered some optimizations, some of which are in this
release and others which I will work on for future releases.
Enjoy,
Robert love
Changes since 20020113 release:
- rename preempt_is_disabled to preempt_get_count (me)
- remove preempt_prefetch, it does more harm than good (Ingo Molnar)
- optimize preempt_enable (George Anzinger, Ingo Molnar)
- better locking in sched.c (me)
- fix race on fork (Ingo Molnar)
- fix mismatched locking in new O(1) migration code (me)
- use BUG_ON instead of BUG where applicable (me)
o for 2.4, add BUG_ON macro
- update Documentation/preempt_locking.txt (me)
- misc clean up (me)
next reply other threads:[~2002-01-24 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 9:39 Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 15:31 [PATCH] preemptive kernel Dieter Nützel
2002-01-24 15:55 ` Tom Rini
2002-01-24 17:57 ` Ingo Molnar
2002-01-24 16:05 ` Tom Rini
2002-01-24 18:04 ` Ingo Molnar
2002-01-24 19:11 ` Robert Love
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=1011865141.867.10.camel@phantasy \
--to=rml@tech9.net \
--cc=george@mvista.com \
--cc=kpreempt-tech@lists.sourceforge.net \
--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