From: Con Kolivas <kernel@kolivas.org>
To: linux <linux-kernel@vger.kernel.org>, CK Kernel <ck@vds.kolivas.org>
Subject: 2.6.10-ck4
Date: Fri, 14 Jan 2005 01:07:30 +1100 [thread overview]
Message-ID: <41E680A2.3010000@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
These are patches designed to improve system responsiveness. It is
configurable to any workload but the default ck4 patch is aimed at the
desktop and ck4-server is available with more emphasis on serverspace.
http://ck.kolivas.org/patches/2.6/2.6.10/2.6.10-ck4/
web:
http://kernel.kolivas.org
all patches:
http://ck.kolivas.org/patches/
I recommend all ck3 users upgrade.
2.6.10-ck3 was a brown paper bag release. A poorly considered last
minute change made for some odd starvation problems. For this release I
rewrote a large section of the staircase code that had been troubling me
and been getting steadily worse. In the process I've made the semantics
of resuming an old timeslice much simpler and more predictable.
Changed:
-cfq-ts-19g.diff
+cfq-ts-20.diff
Jens' latest incarnation of the cfq-timeslices patch with i/o priority
support for read and write has much smoother read vs write
characteristics now.
Added:
+s10_test1.diff
+s10_s10.1.diff
+s10.1_s10.2.diff
+s10.2_s10.3.diff
Staircase updates
+1504_vmscan-writeback-pages.patch
A fix for more oom-kill problems.
Thanks to the many people involved in testing the staircase changes and
reporting back.
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2005-01-13 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 14:07 Con Kolivas [this message]
2005-01-13 19:07 ` [ck] 2.6.10-ck4 Rodney Gordon II
2005-01-13 22:55 ` 2.6.10-ck4 Christian Axelsson
2005-01-14 1:02 ` 2.6.10-ck4 Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 17:33 2.6.10-ck4 Alexey Dobriyan
2005-01-14 1:19 ` 2.6.10-ck4 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=41E680A2.3010000@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