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>
Subject: 2.4.21-ck3
Date: Mon, 23 Jun 2003 14:17:25 +1000	[thread overview]
Message-ID: <200306231418.12060.kernel@kolivas.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Updated patchset.

http://kernel.kolivas.org

Contains:
O(1) + batch scheduling
Interactivity changes
Preempt
Low Latency
CK VM hacks
Swap Prefetch
Read Latency2
Variable HZ
Scheduler tunables
Supermount-NG v1.2.7
XFS file system 1.3.0pre2
ACPI 20030522
Nvidia Nforce2
Bootsplash 
Grsec 1.9.9h

available, less tested, incomplete, or b0rken:
Packet writing for cdrw/dvd-r
CPU Frequency scaling
Software Suspend

Other VMs (yet to be resynced to ck3, but will be soon):
AA VM
Rmap15j

Changes:
I've added my interactivity changes to this one to improve system 
responsiveness, and virtually eliminate audio/video skipping, and to retain X 
interactivity under load (see threads in lkml for full discussion of 
sleep_decay patch).
Timeslices have been restored to their larger values and the interactive feel 
helped by granularity at 10ms.
The scheduler code has been tidied up now that I had been looking at it for so 
long working on my additions I couldn't stand it being untidy.
HZ has been tuned now to 1000 as the above changes make this value not cause 
the jerkiness evident in most 1000Hz kernels. The advantage is much lower 
absolute latencies (see website for benchmarks.)
The extra patches have been incorporated into the full patch now that I've had 
people testing them and bugfixes have been included.
Packet writing is available again separately.

What happened to ck2? Long story involving not enough sleep and posting a dud 
patch. This is what ck2 was supposed to be...

Thanks to all those people who have been aggressively testing the ck2 pre 
patches, and those sending me patch cleanups.

Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+9n9YF6dfvkL3i1gRAnvBAJ4oYKziAUmvCA8zal7dRKB0w7B+RQCeMKZ+
3mAGOFvFKY1G13U/DpEK/0I=
=D1Iq
-----END PGP SIGNATURE-----


             reply	other threads:[~2003-06-23  4:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23  4:17 Con Kolivas [this message]
2003-06-24 19:44 ` 2.4.21-ck3 Toplica Tanasković
2003-06-24 20:25   ` 2.4.21-ck3 Daniel Gryniewicz

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=200306231418.12060.kernel@kolivas.org \
    --to=kernel@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