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 list <ck@vds.kolivas.org>, Ingo Molnar <mingo@elte.hu>,
	Mike Galbraith <efault@gmx.de>, Al Boldi <a1426z@gawab.com>,
	Peter Williams <pwil3058@bigpond.net.au>,
	Nick Piggin <npiggin@suse.de>, Matt Mackall <mpm@selenic.com>,
	Bill Huey <billh@gnuppy.monkey.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Willy Tarreau <w@1wt.eu>, Gene Heskett <gene.heskett@gmail.com>
Subject: [ANNOUNCE] Staircase Deadline cpu scheduler version 0.46
Date: Mon, 23 Apr 2007 01:03:14 +1000	[thread overview]
Message-ID: <200704230103.15265.kernel@kolivas.org> (raw)

Yet another significant bugfix for SMP balancing was just posted for the 
staircase deadline cpu scheduler which improves behaviour dramatically on any 
SMP machine.

Thanks to Willy Tarreau for noticing more bugs.

As requested was a version in the Makefile so this version of the patch 
adds -sd046 to the kernel version.

http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc7-sd-0.46.patch
http://ck.kolivas.org/patches/staircase-deadline/2.6.20.7-sd-0.46.patch

Renicing X to -10, while not essential, may be desirable on the desktop. 
Unlike the CFS scheduler which renices X without your intervention to 
nice -19, the SD patches do not alter nice level on their own.

See the patch just posted called 'sched: implement staircase deadline 
scheduler load  weight fix' for details of the fixes.

Thanks to all testing and giving feedback.

Well I'm exhausted...

-- 
-ck

             reply	other threads:[~2007-04-22 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 15:03 Con Kolivas [this message]
2007-04-22 17:58 ` [ANNOUNCE] Staircase Deadline cpu scheduler version 0.46 Thomas Backlund
2007-04-22 21:21   ` Con Kolivas
     [not found] ` <6700d24e0704221809v572cff44n52b30b3930fd79cf@mail.gmail.com>
2007-04-23  1:59   ` Fwd: [ck] " hechacker1

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=200704230103.15265.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=a1426z@gawab.com \
    --cc=billh@gnuppy.monkey.org \
    --cc=ck@vds.kolivas.org \
    --cc=efault@gmx.de \
    --cc=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=w@1wt.eu \
    --cc=wli@holomorphy.com \
    /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