Re: [Patch] export sched_setscheduler() for kernel module use

[Ingo Molnar]

* Dean Nelson <dcn@xxxxxxx> wrote:

> > another potential API would be to use the linear priority range that the
> > scheduler has internally, from 0 (RT prio 99) to 140 (nice +19). I'm not
> > sure which solution is the better one. Using the linear priority has the
> > advantage of not having to pass any policy value - priorities between 0
> > and 99 implicitly mean SCHED_FIFO, priorities above that would mean
> > SCHED_NORMAL, a pretty natural and compact interface.
> 
> I realize that I don't know where you are ultimately headed with your
> ideas for scheduling changes, but as things are it doesn't make sense
> to me to drop the SCHED_RR scheduling policy. There may be existing
> users who depend on the preemptive nature of this policy. It seems too
> much of a risk to eliminate this policy at this time.

agreed ... that's the weak point. Oh well. So this leaves your original
patch. If someone wants to change the nice value it can be done
separately. I.e. roughly the same API for kernelspace as for userspace.

	Ingo
-
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/