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>
Cc: ck kernel mailing list <ck@vds.kolivas.org>
Subject: Staircase cpu scheduler and -ck updates
Date: Wed, 07 Jul 2004 23:45:22 +1000	[thread overview]
Message-ID: <40EBFE72.7050908@kolivas.org> (raw)

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

Hi all

A tiny SCHED_FIFO microoptimisation and comments changes make up the 
staircase7.9 patch. I doubt anyone will notice any difference, but this 
shows the relative stability/maturity of the scheduler now. Patches for 
vanilla, 2.6.7-bk20 and 2.6.7-mm6 are available. The sched batch (idle 
scheduling) and sched iso (soft real time scheduling) policies are also 
available, stable and ready for prime time testing.

The sched batch and sched iso policies have been updated slightly. The 
sched batch implementation should be safe for disk intensive loads while 
still minimising it's cpu usage as much as possible.

I've resynced with 2.6.7-bk20 as the bk19 introduced the security fixes 
so if you feel you need the security updates you should move to this 
snapshot.

There was a small cfq bug Jens has just addressed and I've added the 
incremental fix to that in the ck-dev, mm6 and bk20 snapshots. If you 
use cfq (ck does by default) it is probably worth applying this fix.

Kernel homepage here:
http://kernel.kolivas.org

Patches available here:
http://ck.kolivas.org/patches/2.6/2.6.7/

Cheers,
Con

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

                 reply	other threads:[~2004-07-07 13:45 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=40EBFE72.7050908@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