Documentation states that priorities are inverted.
It also states that the separation between MAX_USER_RT_PRIO and MAX_RT_PRIO
allows kernel threads to have a higher priority if MAX_USER_RT_PRIO <
MAX_RT_PRIO.
I don't see how this is possible because in setscheduler
* Valid priorities for SCHED_FIFO and SCHED_RR are
* 1..MAX_USER_RT_PRIO-1
and the p->static_prio for RT tasks is determined by
p->prio = MAX_USER_RT_PRIO-1 - p->rt_priority;
so the static_prio for a RT task has a range: [0 ... MAX_USER_RT_PRIO - 2 ]
Fluctuating MAX_USER_RT_PRIO will never prevent a RT process from accessing
the bottom of the priority range. And lower means higher priority.
What am I misunderstanding?
Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/