On Wed, Jun 07, 2006 at 08:53:53AM -0400, Paul Davis wrote:
on POSIX-ish operating systems, there are two
orthogonal aspects to
scheduling: scheduling class and scheduling priority. priority only
ranks different execution contexts (kernel threads) within the *same*
scheduling class - it has no impact when a scheduling decision has to be
made between two execution contexts in two different classes. put
differently, you can leave yourself in SCHED_OTHER (the default class)
and raise your priority to the maximum, but you will never ever be
scheduled to run if there is a SCHED_FIFO thread ready to run even if
its numerical priority is lower than yours.
there is no reason to use setpriority() for realtime work:
sched_setscheduler's parameter argument defines the priority.
Well, my code is cleaner now at least then.