RTEMS | cpukit: Use CONFIGURE_MAXIMUM_PRIORITY with EDF (!831)

Mon Nov 17 23:20:53 UTC 2025

Gedare Bloom commented on a discussion on testsuites/sptests/spedfsched03/system.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831#note_136060

 >  
 >  #define CONFIGURE_MAXIMUM_TASKS               7
 >  #define CONFIGURE_MAXIMUM_PERIODS             10
 > +#define CONFIGURE_MAXIMUM_PRIORITY            512

No guidance, and it doesn't need to be a power-of-2, because the implementation uses a red-black tree. The default is still 256 priority levels. Those are scheduled as background tasks at a lower priority than any task that has a deadline. The way that is done is internal to the scheduler implementation.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831#note_136060
You're receiving this email because of your account on gitlab.rtems.org.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251117/1a19cbf6/attachment-0001.htm>