From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] (Updated) Preemptible Kernel
Date: 06 Sep 2001 18:02:06 -0400 [thread overview]
Message-ID: <999813729.2039.9.camel@phantasy> (raw)
Available at (about 29K):
http://tech9.net/rml/linux/patch-rml-2.4.10-pre4-preempt-kernel-1
http://tech9.net/rml/linux/patch-rml-2.4.9-ac9-preempt-kernel-1
for kernel 2.4.10-pre4 and 2.4.9-ac9, respectively.
Changes since previous post:
* update for new kernels
* fix newline/space format buglet
Changes since original patch:
* fix compile bug -- CONFIG_HAVE_DEC_LOCK is set as needed, now.
This patch allows a new config setting, CONFIG_PREEMPT (set in
`Processor Type and Features') that enables a fully preemptible kernel.
Preemption is controled via SMP lock points. Control of execution is
yielded to higher processes even if the currently running process is in
kernel space.
This should increase response and decrease latency, and is a highly
recommended patch for real-time, audio, and embedded systems. However,
it is recommended for anyone. I use it on my everyday workstation.
An interesting new article on a preemptible kernel in linux is available
at:
http://www.linuxdevices.com/articles/AT5152980814.html
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next reply other threads:[~2001-09-06 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 22:02 Robert Love [this message]
2001-09-06 20:39 ` [PATCH] (Updated) Preemptible Kernel Phillip Susi
2001-09-07 0:58 ` Robert Love
2001-09-07 1:10 ` Daniel Phillips
2001-09-09 4:44 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-09 22:38 Robert Love
2001-09-19 0:10 Robert Love
2001-09-19 7:18 ` Robert Love
2001-10-01 4:21 Robert Love
2001-10-01 5:34 ` Steve Kieu
2001-10-01 5:46 ` 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=999813729.2039.9.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