From: Robert Love <rml@tech9.net>
To: Christoph Lameter <christoph@lameter.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Preemptive patch success 2.4.10-pre4 + lots of other patches
Date: 07 Sep 2001 00:45:59 -0400 [thread overview]
Message-ID: <999837964.865.3.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0109062135280.1643-100000@devel.office>
In-Reply-To: <Pine.LNX.4.33.0109062135280.1643-100000@devel.office>
On Fri, 2001-09-07 at 00:36, Christoph Lameter wrote:
> Given the minimal nature of the patch I would suggest that it become part
> of 2.4.10 or 11
Are you kidding? We will be lucky to see this in during 2.5.
Its a pretty big change. It makes the Linux kernel preemptible. This
is a fairly big move, one I don't think any of the major Unices have
done. The only reason the patch is not _huge_ is because the Linux
kernel is already setup for concurrency of this nature -- it does SMP.
I suggest you read
http://www.linuxdevices.com/articles/AT4185744181.html
http://www.linuxdevices.com/articles/AT5152980814.html
http://kpreempt.sourceforge.net
and my previous threads on this issue, for more informaiton.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-07 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <999835218.2456.16.camel@phantasy>
2001-09-07 4:36 ` Linux Preemptive patch success 2.4.10-pre4 + lots of other patches Christoph Lameter
2001-09-07 4:45 ` Robert Love [this message]
2001-09-07 5:19 ` Daniel Phillips
2001-09-07 5:20 ` Robert Love
2001-09-07 5:35 ` Daniel Phillips
2001-09-07 5:36 ` Robert Love
2001-09-07 12:56 ` Chris Ricker
2001-09-07 12:31 ` safemode
2001-09-07 2:44 Christoph Lameter
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=999837964.865.3.camel@phantasy \
--to=rml@tech9.net \
--cc=christoph@lameter.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.