From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck kernel mailing list <ck@vds.kolivas.org>
Subject: 2.6.8.1-ck5
Date: Sat, 28 Aug 2004 01:26:41 +1000 [thread overview]
Message-ID: <412F52B1.6030008@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Patchset update. These are patches designed to improve system
responsiveness with specific emphasis on the desktop, but configurable
to any workload.
Web site with faq:
http://kernel.kolivas.org
Patches (with split-out also):
http://ck.kolivas.org/patches/2.6/2.6.8.1/2.6.8.1-ck5/
Added since ck4:
+s8.0_s8.1
Sync with latest staircase patch. Tiny fix affecting very short running
tasks that use a lot of cpu (like xmame).
+mapped_watermark_fix.diff
+sc_mw.diff
Mapped watermark was released a touch too early and was too aggressive
leading to an oom easily. These fix that, make it more efficient and
make it possible to properly inactivate it by setting mapped to 0.
+1g_change_config.diff
Change the 1Gb lowmem so that the default is off (thanks for suggestion
Michael Buesch)
Full patchlist:
from_2.6.8.1_to_staircase8.0.bz2
schedrange.diff
schedbatch2.4.diff
schediso2.5.diff
sched-adjust-p4gain
mapped_watermark.diff
defaultcfq.diff
config_hz.diff
1g_lowmem_i386.diff
akpm-latency-fix.patch
9000-SuSE-117-writeback-lat.patch
cddvd-cmdfilter-drop.patch
cool-spinlocks-i386.diff
bio_uncopy_user-mem-leak.patch
bio_uncopy_user2.diff
ioport-latency-fix-2.6.8.1.patch
supermount-ng204.diff.bz2
fbsplash-0.9-r5-2.6.8-rc3.patch.bz2
make-tree_lock-an-rwlock.patch.bz2
invalidate_inodes-speedup.patch
2.6.8.1-mm2-reiser4.diff.bz2
s8.0_s8.1
mapped_watermark_fix.diff
sc_mw.diff
1g_change_config.diff
2.6.8.1-ck5-version.diff
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
reply other threads:[~2004-08-27 15:30 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=412F52B1.6030008@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