public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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-ck7
Date: Fri, 10 Sep 2004 14:02:45 +1000	[thread overview]
Message-ID: <41412765.4010005@kolivas.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]

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.8.1/2.6.8.1-ck7/patch-2.6.8.1-ck7.bz2

web:
http://kernel.kolivas.org
all patches:
http://ck.kolivas.org/patches/
Split patches and a server specific patch available.


Added since ck5 (last announced release):
-change_reiser4_config.diff
Make default reiser 4 off and not configurable if 4k stacks is on

-lenient_uw.diff
Mapped watermark was too aggressive with freeing ram. Balance is just 
about right with this being a watermark just above "high" used by kswapd

-s8.1_test1
-s8.1test1_test2
-s8.1_smtfix
Numerous small fixes for the staircase code to not fool the "burst" 
mechanism. This helps simulated hardware (wine, mame, zsnes) a lot.

-write-barriers.patch
File system write barriers added for cfq2

-cfq_iosched_v2.patch
Updated Completely Fair Queueing I/O scheduler by Jens Axboe

-vesafb-tng-0.9-rc4-r2-2.6.8.1.patch
New vesa framebuffer for more modes at console and changing resolution 
on the fly
-vesafb_change_config.diff
Make the default off for compatibility purposes.

-back_journal_clean_checkpoint_list-latency-fix.patch
A small latency hack by akpm was found to be questionable; back it out.
-2.6.8.1-ck7-version.diff


Changed:
-supermount-ng205.diff
Compile fixes for gcc3.4+


Full patch list:

from_2.6.8.1_to_staircase8.0
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-ng205.diff
fbsplash-0.9-r5-2.6.8-rc3.patch
make-tree_lock-an-rwlock.patch
invalidate_inodes-speedup.patch
2.6.8.1-mm2-reiser4.diff
change_reiser4_config.diff
s8.0_s8.1
mapped_watermark_fix.diff
sc_mw.diff
1g_change_config.diff
lenient_uw.diff
s8.1_test1
s8.1test1_test2
s8.1_smtfix
write-barriers.patch
cfq_iosched_v2.patch
vesafb-tng-0.9-rc4-r2-2.6.8.1.patch
vesafb_change_config.diff
back_journal_clean_checkpoint_list-latency-fix.patch
2.6.8.1-ck7-version.diff


Cheers,
Con Kolivas

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

             reply	other threads:[~2004-09-10  4:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  4:02 Con Kolivas [this message]
2004-09-13  1:23 ` 2.6.8.1-ck7, Two Badnessess, one dump Joshua Schmidlkofer
2004-09-13  3:51   ` [ck] " Con Kolivas
2004-09-13 15:21     ` Joshua Schmidlkofer
2004-09-13 19:12       ` Jens Axboe
2004-09-14  3:45         ` Joshua Schmidlkofer
2004-09-15  7:21           ` Jens Axboe
2004-09-14  3:46         ` Joshua Schmidlkofer
2004-09-15  7:21           ` Jens Axboe
2006-01-14  2:19       ` Con Kolivas

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=41412765.4010005@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