Why do you say only root? Since the schedule type and priority are
inherited one only needs to be root to set the progenitors real time
priority. Also, a programs priority/ schedule type can be set by
another (root) program without the target program being root. I
routinely set inetd to real time, for example, to let telnet sessions
run at real time.
> I don't think it makes too much sense to have
> an global rt queue on a multi processor system, but there should be some
> way to define "scheduling groups" where rt semantics are followed inside.
Still, the customer is king.
> Such a scheduling group could be a clone flag or default to CLONE_VM for
> example for compatibility. A scheduling group would also make it possible
> to support simple rt semantics for thread groups as non root. Then one
> could run a rt queue per scheduling group, and simulate global rt run queue
> or per cpu rt run queue as needed by appropiate setup.
My first thought is that this is fairly high overhead to put in the
schedule path. May be if I knew more....
-- George firstname.lastname@example.org High-res-timers: http://sourceforge.net/projects/high-res-timers/ Real time sched: http://sourceforge.net/projects/rtsched/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/