[Bug 1636] Refactor Rate Monotonic Manager into a generic Periodic Manager

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=1636

--- Comment #6 from Gedare <giddyup44 at yahoo.com> 2010-07-28 08:56:42 CDT ---
(In reply to comment #5)
> We should wait with trivial file renames until we have a Version Control System
> that supports this.  This rename and modify patches make it very hard to see
> the actual differences.

I'd like to get this merged, since it puts periodic task management into the
supercore and enables me to write schedulers that support periodic tasks.

What I did in this patch is to move all of the functionality of
_Rate_monotonic_XXX in cpukit/rtems to _Periodic_XXX in cpukit/score, and all
of the functionality of rate_monotonic_xxx in cpukit/rtems to periodic_xxx in
cpukit/rtems.  I think turned every rate_monotonic_xxx into a wrapper for the
periodic_xxx function, and deleted all of the _Rate_monotonic_XXX functions
(they shouldn't be used by user applications, right?).  I also changed the
names and declarations of data structures to be in the Periodic manager and
provide typedefs in the rate monotonic code.  The change to the enum for the
period state caused changes in some of the testcases that directly use the
state value.

It is possible for me to write another scheduling algorithm for periodic tasks
that uses the rate monotonic interface. However, those schedulers won't be
encapsulated neatly in the supercore.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.