Abstract
The TARTAR CGN-36/NTU Baseline Development Program (CGN-36) required a preemptive scheduling mechanism that was both efficient and compatible with an Ada implementation targeted for the m68020 processor. As a result, CGN-36 developed an event-driven asynchronous scheduling package functioning as an extension of the selected vendor's (Systems Designers (SD)) Ada Run-Time Environment (RTE). This paper describes:Introduction. Why a standard Ada (rendezvous) approach would not work1. Synchronous versus Asynchronous trade-offs2. Design of the event-driven scheduler3. Validation issues4. Timing results5. Porting/Reuse issues6. Lessons learned
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
