From: Eric Hustvedt <lkml@plumlocosoft.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.28-lck1
Date: Fri, 03 Dec 2004 17:57:46 -0500 [thread overview]
Message-ID: <1102114666.31017.5.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
I have updated the lck patchset. This is the patchset formerly known as
the 2.4-ck patchset. I apologize for the long delay in releasing this
patch, but paid work had to come first.
http://www.plumlocosoft.com/kernel/
Includes:
O(1) scheduler with batch scheduling, interactivity
Preemptible kernel
Low Latency
Read Latency2
Variable Hz
64-bit jiffies
Supermount-NG v1.2.11a
Bootsplash v3.0.7
POSIX ACL/xattr v0.8.71
POSIX extended security attributes v0.8.71
NTFS file system v2.1.6b
Updated:
- I have merged PPC fixes for the O(1) scheduler and the variable hertz
patch, so 32-bit PPC kernels should work now.
- I have attempted to make the patchset gcc 3.4 compatible. If I have
missed anything, let me know.
Pending:
- GRsec update to version 2.0.2.
-Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-12-03 23:01 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=1102114666.31017.5.camel@localhost \
--to=lkml@plumlocosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox