From: tabris <tabris@tabris.net>
To: "Ernest L. Williams Jr." <ernesto@ornl.gov>
Cc: linux-kernel@vger.kernel.org, Robert Love <rml@ximian.com>
Subject: Re: Issues for "CONFIG_PREEMPT"
Date: Sun, 9 May 2004 16:06:11 -0400 [thread overview]
Message-ID: <200405091606.13567.tabris@tabris.net> (raw)
In-Reply-To: <1084076781.3424.104.camel@matrix>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 09 May 2004 12:26 am, Ernest L. Williams Jr. wrote:
> Hi,
>
> Please CC me as I am not subscribed to the list.
>
> Are the kernel developers working on the preemptive kernel in 2.6?
>
> Initially the preempt patch was heavily advertised as one of the new
> enhancements for the 2.6 kernel.
>
> What is the current status? I am not able to find any "detailed"
> information about this.
>
> Could someone please summarize the issues and plans for the preempt
> patch?
I believe the relevant point is that it is no longer a 'patch' but merged in
mainline 2.6. in fact, it was merged early-mid 2.5 (don't know the precise
version, didn't pay that much attn).
>
>
Unfortunately for those of us who still like the 2.4 kernel, the Preempt patch
for 2.4 (previously maintained by Robert Love) is, to my knowledge, no longer
maintained except by some distros. The official stance is that everybody
should go with 2.6. And as the preempt patch is not something that can be
trivially ported/maintained (requiring intimate knowledge of internals), it
shall likely remain so.
>
> Thanks,
> Ernesto
- --
tabris
- -
Hardware, n.:
The parts of a computer system that can be kicked.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAno801U5ZaPMbKQcRAg/UAKClO/ZOAS27in6oXxg3AXY2y1Yp0ACgqYbm
kv9RoTF/qiO+GyIyoxKHjlE=
=kyiQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-09 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 4:26 Issues for "CONFIG_PREEMPT" Ernest L. Williams Jr.
2004-05-09 20:06 ` tabris [this message]
2004-05-10 0:02 ` 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=200405091606.13567.tabris@tabris.net \
--to=tabris@tabris.net \
--cc=ernesto@ornl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@ximian.com \
/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