SMP
From RTEMSWiki
|
|---|
SMP Support in RTEMS
Status: Ongoing.
Introduction: TODO: Introduce the main concepts around the project: Theoretical preliminaries, preexisting RTEMS capabilities used or augmented (if any), important concepts, problems/needs the project will try to solve/satisfy.
Goal: TODO: Concise statement of the overall goal of the project. Refine this initial statement to include: project deliverables (code, docs, testing), required/suggested methodology, standards of quality, possible goal extensions beyond the main objective.
Requirements: TODO: List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills.
Resources: TODO: Current RTEMS developers, papers, etc that may help you in this project.
Acknowledgements
- who helped add work
Subtasks
- Provide common names for various bsp_delay() routines. Currently not all BSPs have even a default crude, inaccurate implementation. Those that do have an implementation, do not have consistent names or time units.
- Move deferred memory free support to Heap from Malloc. This will eliminate a potential race condition when deleting self on one CPU and creating a new thread on another CPU.
- Add test for SMP timeslicing - Needed to ensure SMP timeslicing correctness.
- Add processor affinity - Need to define API and implement.
Miscellaneous Sections
As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO.
References
- TBD
Other sections: If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.