[ANNOUNCE][RFC] PlugSched-6.4 for 2.6.19

[ANNOUNCE][RFC] PlugSched-6.4 for 2.6.19

[Al Boldi]

Peter Williams wrote:
>
> This version removes the hard/soft CPU rate caps from the SPA schedulers.
>
> A patch for 2.6.19 is available at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.4-for-2.6.19.patch?d
>ownload>
>
> 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>/

Thanks for keeping this patch in sync with the kernel.

I tried spa_ebs and it still has some hang-ups under load.  Setting 
iab_incr_threshold to 1000 smoothes this, but an obvious mouse-jitter can 
still be observed.

Any hope this could be addressed?


Thanks!

--
Al

[ANNOUNCE][RFC] PlugSched-6.4 for 2.6.19

[Peter Williams]

This version removes the hard/soft CPU rate caps from the SPA schedulers.

A patch for 2.6.19 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-6.4-for-2.6.19.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,
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@bigpond.net.au

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