From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>,
CK Kernel <ck@vds.kolivas.org>
Subject: 2.6.9-ck1
Date: Tue, 19 Oct 2004 21:13:31 +1000 [thread overview]
Message-ID: <4174F6DB.3000304@kolivas.org> (raw)
These are patches designed to improve system responsiveness with
specific emphasis on the desktop, but configurable to any workload.
http://ck.kolivas.org/patches/2.6/2.6.9/2.6.9-ck1/patch-2.6.9-ck1.bz2
web:
http://kernel.kolivas.org
all patches:
http://ck.kolivas.org/patches/
Split patches and a server specific patch available.
Added:
+block_fix.diff
A small fix for congestion which was causing stalls under heavy i/o load.
+269rc4-mingo_ll.diff
+269rc4-mingo-bkl.diff
The low latency hacks in current -mm releases by Ingo Molnar, including
the preemptible big kernel lock
+ll-config.diff
Default the preemptible kernel lock off
+nvidia_compat.diff
This allows the current version of the evil binary nvidia drivers to
compile.
+buildfix.diff
This is a last minute fix for 2.6.9 that causes internal compiler errors
+269ck1-version.diff
Version
Changed:
~2.6.9_to_staircase9.0.diff
Latest version of staircase cpu scheduler. This is version8.K renamed in
line with kernel release. There are no known bugs with this release. The
main changes since last -ck released staircase are significantly better
handling of subjiffy timeslices, and much larger timeslices for -niced
processes as per mainline.
~schedbatch2.5.diff
~schediso2.8.diff
Resync with latest staircase.
~mwII.diff
The mapped watermark code was incompatible with newer vm changes so it
was rewritten and is much less likely to cause oom. The same sysctls
still exist (vm.mapped and vm.hardmaplimit), but the hardmaplimit is off
by default. If you still have large amounts of swapping under heavy disk
i/o I recommend turning this on.
~cfq2-20041019.patch
One small bugfix.
Full patchlist:
2.6.9_to_staircase9.0.diff
schedrange.diff
schedbatch2.5.diff
schediso2.8.diff
mwII.diff
1g_lowmem1_i386.diff
cfq2-20041019.patch
block_fix.diff
defaultcfq.diff
269rc4-mingo_ll.diff
269rc4-mingo-bkl.diff
ll-config.diff
cddvd-cmdfilter-drop.patch
nvidia_compat.diff
buildfix.diff
269ck1-version.diff
Cheers,
Con Kolivas
next reply other threads:[~2004-10-19 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 11:13 Con Kolivas [this message]
2004-10-19 12:27 ` [ck] 2.6.9-ck1 Tero Grundström
2004-10-19 12:30 ` 2.6.9-ck1 Con Kolivas
2004-10-19 12:37 ` [ck] 2.6.9-ck1 Walt
2004-10-19 12:35 ` [ck] 2.6.9-ck1 Stuart Longland
2004-10-19 12:51 ` Tero Grundström
2004-10-20 2:06 ` Gene Heskett
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=4174F6DB.3000304@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--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