[ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2

[ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2

[Peter Williams]

This version contains minor code cleanups and more modifications to the 
spa_ws scheduler to improve its interactive responsiveness.  This 
modification includes control parameters for the identification of 
"media streaming" tasks.  The default values for these parameters are 
set based on observations of RealPlayer and the parameters of the video 
and audio benchmarks in Con Kolivas's interbench test and, therefore, 
may need adjusting for other programs.

A patch for 2.6.13-mm2 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.13-mm2.patch?download>

and a patch to upgrade the 6.1 for 2.6.13 to 6.1.1 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1-to-6.1.1-for-2.6.13.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 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

oops plugsched, spa_ws, scsi, sata, ata_piix, threading 2.6.13-mm2

[Michal Piotrowski]

Hi,

[1.] One line summary of the problem:
Oops when starting system.

[2.] Full description of the problem/report:
Kernel boot params:
kernel /vmlinuz-2.6.13-mm2 root=/dev/sda1 ro cpusched=spa_ws

[3.] Keywords (i.e., modules, networking, kernel):
plugsched, spa_ws, scsi, sata, ata_piix, threading

[4.] Kernel version (from /proc/version):
Linux version 2.6.13-mm2 (root@ng02.pl) (gcc version 3.3.5 (Debian
1:3.3.5-13)) #3 SMP PREEMPT Sun Sep 11 14:20:57 CEST 2005

[5.] Output of Oops
Process ksoftirqd/0 (pid: 3, threadinfo=c03e3000 task=c195e620)

Stack: c01f870f f7d0f24c f7d0f24c c1bccc80 f7d0e9e8 00000202 c0274562 f2d0e9e8
       00000000 00000024 00000001 00040000 00000024 c1bccc80 c02748e5 c1bccc80
       00000000 00000024 00000001 00000000 00000000 00000000 f7d0e9e8 00000024

Call trace:
[<c01f870f>] kobject_put+0x1f/0x30
[<c0274562>] scsi_end_request+0xd2/0xf0
[<c02748e5>] scsi_io_competition+0x235/0x460
[<c0274de5>] scsi_generic_done+0x35/0x50
[<c026f9ee>] scsi_finish_command+0x7e/0xa0
[<c026f8a0>] scsi_softirq+0xd0/0x150
[<c0125ee3>] tasklet_action+0x73/0xe0
[<c0125b86>] __do_softirq+0xd6/0xf0
[<c01055af>] do_softirq+0x4f/0x60
=======================
[<c0126165>] ksoftirqd+0x95/0x100
[<c01260d0>] ksoftirqd+0x0/0x100
[<c01367ba>] kthread+0xba/0xc0
[<c0136700>] kthread+0x0/0xc0
[<c0101275>] kernel_thread_helper+0x5/0x10

Code: 7d 07 00 89 44 24 04 89 1c 24 e8 67 69 ff ff ff eb a5 90 8d 74
26 00 55 57 56 53 83 ec 08 86 44 24 1c 89 44 24 04 8b 80 f8 00 00 00
<8b> 38 f6 80 7d 01 00 00 80 0f 85 96 00 00 00 8b 47 34 8d 6f 24

<0> Kernel panic - not syncing: Fatal exception in interrupt



  _|_|                _|
_|    _|  _|  _|_|  _|_|_|_|
_|    _|  _|_|        _|
_|    _|  _|          _|
  _|_|    _|            _|_|
OOPS Reporting Tool v.b5
www.wsi.edu.pl/~piotrowskim/
/files/ort/beta/

Regards,
Michal Piotrowski

Re: oops plugsched, spa_ws, scsi, sata, ata_piix, threading 2.6.13-mm2

[Peter Williams]

Michal Piotrowski wrote:
> Hi,
> 
> [1.] One line summary of the problem:
> Oops when starting system.
> 
> [2.] Full description of the problem/report:
> Kernel boot params:
> kernel /vmlinuz-2.6.13-mm2 root=/dev/sda1 ro cpusched=spa_ws

Could you please confirm that this only occurs with cpusched=spa_ws and 
not with any of the other schedulers?  In particular, if you could try 
it for ingosched, staircase and spa_no_frills I would appreciate it.

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

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

Re: oops plugsched, spa_ws, scsi, sata, ata_piix, threading 2.6.13-mm2

[Michal Piotrowski]

Hi,

On 12/09/05, Peter Williams <pwil3058@bigpond.net.au> wrote:
> Could you please confirm that this only occurs with cpusched=spa_ws and
> not with any of the other schedulers?  In particular, if you could try
> it for ingosched, staircase and spa_no_frills I would appreciate it.

It must be scsi problem. I do some tests (boot, reboot) with all
schedulers (5 times for every scheduler) and the same oops appeared
with staircase - but only once.

Regards,
Michal Piotrowski

Re: [ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2

[Peter Williams]

Peter Williams wrote:
> This version contains minor code cleanups and more modifications to the 
> spa_ws scheduler to improve its interactive responsiveness.  This 
> modification includes control parameters for the identification of 
> "media streaming" tasks.  The default values for these parameters are 
> set based on observations of RealPlayer and the parameters of the video 
> and audio benchmarks in Con Kolivas's interbench test and, therefore, 
> may need adjusting for other programs.
> 
> A patch for 2.6.13-mm2 is available at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.13-mm2.patch?download> 
> 
> 
> and a patch to upgrade the 6.1 for 2.6.13 to 6.1.1 is available at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1-to-6.1.1-for-2.6.13.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 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

A patch for 2.6.14-rc1 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.14-rc1.patch?download>

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

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

Re: [ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2

[Peter Williams]

Peter Williams wrote:
> This version contains minor code cleanups and more modifications to the 
> spa_ws scheduler to improve its interactive responsiveness.  This 
> modification includes control parameters for the identification of 
> "media streaming" tasks.  The default values for these parameters are 
> set based on observations of RealPlayer and the parameters of the video 
> and audio benchmarks in Con Kolivas's interbench test and, therefore, 
> may need adjusting for other programs.
> 
> A patch for 2.6.13-mm2 is available at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.13-mm2.patch?download> 
> 
> 
> and a patch to upgrade the 6.1 for 2.6.13 to 6.1.1 is available at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1-to-6.1.1-for-2.6.13.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 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

Patches for 2.6.14-rc2 and 2.6.14-rc2-mm1 are available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.14-rc2.patch?download>

and

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.14-rc2-mm1.patch?download>

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

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