Re: [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2

[Peter Williams]

Al Boldi wrote:
> Peter Williams wrote:
> > This version removes the hard/soft CPU rate caps from the SPA schedulers.
> >
> > A patch for 2.6.18-rc2 is available at:
> >
> > <http://prdownloads.sourceforge.net/cpuse/plugsched-6.4-for-2.6.18-rc2.pat
> > ch?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>
>
> Any reason dynsched couldn't be merged with plugsched?

None that I know of (but I'm not familiar with dynsched).  Patches to 
add it to the mix would be accepted and once in I would try to keep it 
in step with kernel changes.

> > 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
>
> It may be really great, to allow schedulers perPid parent, thus allowing the 
> stacking of different scheduler semantics.  This could aid flexibility a 
> lot.

I'm don't understand what you mean here.  Could you elaborate?

> Worth a try, and should be easy to implement.
>
> > Control parameters for the scheduler can be read/set via files in:
> >
> > /sys/cpusched/<scheduler>/
>
> Thanks for the most important out-of-tree patch that makes 2.6 reasonable.

My pleasure,
Peter
--
Peter Williams                                   pwil3058@xxxxxxxxxxxxxx

"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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/