linux-kernel - [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4636E6A5.8040102@bigpond.net.au>
Date:	Tue, 01 May 2007 17:05:09 +1000
From:	Peter Williams <pwil3058@...pond.net.au>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	William Lee Irwin III <wli@...omorphy.com>
CC:	Chris Han <xiphux@...il.com>, Con Kolivas <kernel@...ivas.org>,
	Jake Moilanen <moilanen@...tin.ibm.com>,
	Paolo Ornati <ornati@...twebnet.it>,
	Ingo Molnar <mingo@...e.hu>
Subject: [ANNOUNCE][RFC] PlugSched-6.5.1 for  2.6.21

The main change in this version is to fix bugs introduced to SPA 
schedulers during modifications to handle a recent change to the 
scheduler driver interface to take account of recent changes to the load 
balancing code.

This patch also includes a patch to sis900 code to enable it to boot on 
my system for testing (patch supplied by Neil Horman).

A patch for 2.6.21 is available at:

<http://downloads.sourceforge.net/cpuse/plugsched-6.5.1-for-2.6.21.patch>

and a quilt/gquilt patch series is available at:

<http://downloads.sourceforge.net/cpuse/plugsched-6.5.1-for-2.6.21.patch-series.tar.gz>

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,
ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr, spa_ebs
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@...pond.net.au

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/