public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: Updated preempt-kernel patches
Date: 12 Oct 2001 16:19:36 -0400	[thread overview]
Message-ID: <1002917978.957.86.camel@phantasy> (raw)

Updated preempt-kernel patches for 2.4.10, 2.4.12, 2.4.13-pre1, and
(phew!) 2.4.12-ac1 are available at:

http://tech9.net/rml/linux

Note the patches for 2.4.10 are updated over previously releases.

These patches allow create a preemptible kernel -- increasing system
response time.  Everyone is encouraged to give it a whirl and report
back.

Major changes include code to prevent CPU changes on preempt (should
prevent a class of race conditions), an SMP compile fix, and various
cleanups.

Full change log:

20011011
- remove pgalloc.h preemption disable statements -- not
  needed with the new CPU switch prevention
- fix compile on SMP in some configurations (ac tree only)

20011005
- rearrange sched.c so we can patch cleanly against rtsched
  (or vice versa)

20011004
- prevent the case of preemption causing a CPU switch
  by locking tasks to the current CPU in preempt_schedule
- revert to _raw_spin_xxx from _spin_xxx since PPC uses
  that convention.

20011003
- push pcmcia-cs tools fix into their next release

20011001
- fix spin_lock_prefetch optimization causing (harmless)
  compile warnings

	Robert Love


             reply	other threads:[~2001-10-12 20:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 20:19 Robert Love [this message]
2001-10-12 20:47 ` Updated preempt-kernel patches Robert Love
2001-10-12 22:19 ` Robert Love
2001-10-13  0:27   ` Mike Fedyk
2001-10-13  0:32     ` Robert Love
2001-10-13  1:01       ` Mike Fedyk
2001-10-13  5:31         ` 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=1002917978.957.86.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