From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] updated preempt-kernel
Date: 20 Oct 2001 03:27:12 -0400 [thread overview]
Message-ID: <1003562833.862.65.camel@phantasy> (raw)
Testers Wanted:
patches to enable a fully preemptible kernel are available at:
http://tech9.net/rml/linux
for kernels 2.4.10, 2.4.12, 2.4.12-ac3, and 2.4.13-pre5.
What is this:
A preemptible kernel. It lowers your latency.
What is New:
* sync with new kernel releases
* if HIGHMEM_DEBUG was on the preempt counter would be incremented at
times but never decremented. this resulted in preemption becoming
permanently disabled.
* if HIGHMEM_DEBUG was not on, HIGHMEM would crash the system horribly
due to a case where preemption was enabled without a corresponding
disable.
* reapply dropped hunk to pgalloc to prevent reentrancy onto per-CPU
data
The next few patches are going to work on identifying any remaining
per-CPU variables that need explicit locking under preemption.
Robert Love
next reply other threads:[~2001-10-20 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 7:27 Robert Love [this message]
2001-10-20 12:44 ` [PATCH] updated preempt-kernel elko
2001-10-22 20:43 ` elko
2001-10-22 23:11 ` Robert Love
2001-10-23 15:13 ` elko
2001-10-23 15:40 ` Andre's PDC20269 support patch? J.R. de Jong
2001-10-20 12:59 ` [PATCH] updated preempt-kernel Lorenzo Allegrucci
2001-10-20 17:02 ` Robert Love
2001-10-22 15:32 ` bill davidsen
2001-10-22 18:39 ` Mike Fedyk
2001-10-22 23:08 ` Robert Love
2001-10-21 11:05 ` Colin Phipps
2001-10-21 15:24 ` Andrew Morton
2001-10-21 18:16 ` Robert Love
2001-10-22 15:36 ` Taral
2001-10-21 18:23 ` Federico Sevilla III
2001-10-22 8:27 ` Jesper Juhl
2001-10-22 14:46 ` szonyi calin
2001-10-22 23:03 ` 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=1003562833.862.65.camel@phantasy \
--to=rml@tech9.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;
as well as URLs for NNTP newsgroup(s).