All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Jake Moilanen <moilanen@austin.ibm.com>
Subject: [ANNOUNCE][RFC] PlugSched-6.1.6 for  2.6.15-rc5 and 2.6.15-rc5-mm2
Date: Tue, 13 Dec 2005 17:35:12 +1100	[thread overview]
Message-ID: <439E6BA0.8020302@bigpond.net.au> (raw)

This version features a major gutting of the SPA based schedulers to 
reduce overhead.  The inclusion of the mechanisms for gathering and 
displaying accrued scheduling statistics have been made a compile time 
configurable option (default is exclusion) as they are not an integral 
part of the scheduler and were mainly there to help with tuning.  In a 
future version they will be removed completely.

Additionally, the mechanism for auto detection and preferential 
treatment of media streamers in the spa_ws scheduler has been made a 
compile time option (default is exclusion).  The reason for this is that 
my testing shows that the performance of media streamers on spa_ws is 
adequate without it.  This will also be removed in a future version 
unless requested otherwise.

A patch for 2.6.15-rc5 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.6-for-2.6.15-rc5.patch?download>

and a patch for 2.6.15-rc5-mm2 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.6-for-2.6.15-rc5-mm2.patch?download>

Very Brief Documentation:

You can select a default scheduler at kernel build time.  If you wish to
boot with a scheduler other than the default it can be selected at boot
time by adding:

cpusched=<scheduler>

to the boot command line where <scheduler> is one of: ingosched,
nicksched, staircase, spa_no_frills, spa_ws, spa_svr or zaphod.  If you
don't change the default when you build the kernel the default scheduler
will be ingosched (which is the normal scheduler).

The scheduler in force on a running system can be determined by the
contents of:

/proc/scheduler

Control parameters for the scheduler can be read/set via files in:

/sys/cpusched/<scheduler>/

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

             reply	other threads:[~2005-12-13  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13  6:35 Peter Williams [this message]
2005-12-15 23:28 ` [ANNOUNCE][RFC] PlugSched-6.1.6 for 2.6.15-rc5 and 2.6.15-rc5-mm2 Peter Williams
2005-12-20  0:05 ` Peter Williams
2005-12-25  7:09 ` Peter Williams
2006-01-04  5:20   ` Peter Williams

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=439E6BA0.8020302@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moilanen@austin.ibm.com \
    --cc=wli@holomorphy.com \
    --cc=xiphux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.