mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Cc: kpreempt-tech@lists.sourceforge.net
Subject: [PATCH] preemptible kernel patch for 2.4 and 2.5
Date: 07 Jan 2002 13:16:58 -0500	[thread overview]
Message-ID: <1010427419.1519.24.camel@phantasy> (raw)

Announcing the next revision of the fully preemptible linux kernel
patch, available for 2.4 and 2.5 trees now at:

ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel

and your favorite mirrors.  Diffs for 2.4.18-pre1 and 2.5.2-pre9 are
available along with previous patches.

This patch, which we are all familiar with by now, makes the kernel
preemptible.  This means that a higher priority process can preempt a
lower priority process, even if it is running inside the kernel. 
Reentrancy is protected by SMP lock points.  Despite the warnings to the
contrary about throughput, benchmarking actually shows a marked
increase, probably due to faster scheduling of woken I/O tasks. 
Complexity added is minimal.

ARM, i386, and SH are supported.  UP and SMP is supported.  There are no
outstanding bugs.

Perhaps a feature that is often overlooked is the growth for performance
gains in the future.  As we continue to make locks finer grained (and,
especially, remove the BKL) performance will increase.  Thus we now have
an architecture where by we can continue to improve performance.

Changes:

- (2.5 only) include linux/sched.h in fs/char_dev.c

- SH arch: fix certain code path not hitting preempt_enable (Jeremy
Siegel)

- stop locking task to CPU across preemptions.
 
- back out console race fix as it was merged with mainline

Todo:

- Port the scheduling details to Ingo's O(1) scheduler

Enjoy,

	Robert Love


                 reply	other threads:[~2002-01-07 18:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1010427419.1519.24.camel@phantasy \
    --to=rml@tech9.net \
    --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

all inboxes | Powered by JetHome®