URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Subversion Repositories or1k
[/] [or1k/] [trunk/] [rtems-20020807/] [cpukit/] [posix/] [include/] [rtems/] [posix/] [priority.h] - Rev 1765
Compare with Previous | Blame | View Log
/* * * * priority.h,v 1.5 1997/04/15 18:02:12 joel Exp */ #ifndef __RTEMS_POSIX_PRIORITY_h #define __RTEMS_POSIX_PRIORITY_h #include <rtems/score/priority.h> /* * 1003.1b-1993,2.2.2.80 definition of priority, p. 19 * * "Numericallly higher values represent higher priorities." * * Thus, RTEMS Core has priorities run in the opposite sense of the POSIX API. * * There are only 254 posix priority levels since a task at priority level * 255 would never run because of the RTEMS idle task. This is necessary * because GNAT maps the lowest Ada task priority to the lowest thread * priority. The lowest priority Ada task should get to run, so there is * a fundamental conflict with having 255 priorities. */ #define POSIX_SCHEDULER_MAXIMUM_PRIORITY (254) #define POSIX_SCHEDULER_MINIMUM_PRIORITY (1) RTEMS_INLINE_ROUTINE boolean _POSIX_Priority_Is_valid( int priority ); RTEMS_INLINE_ROUTINE Priority_Control _POSIX_Priority_To_core( int priority ); RTEMS_INLINE_ROUTINE int _POSIX_Priority_From_core( Priority_Control priority ); #include <rtems/posix/priority.inl> #endif