The MARUTI hard real-time operating system

Abstract

The MARUTI operating system is designed to support real-time applications on a variety of hardware systems. The kernel supports objects as primitive entities, and provides a communication mechanism that allows transparent distribution in networked systems. Fault tolerance is provided through replication and consistency-control mechanisms. Most importantly, MARUTI supports guaranteed-service scheduling, in which jobs that are accepted by the system are verified to satisfy general time constraints.Guaranteed-service scheduling means that, given a job with a set of service requirements and time constraints, the system automatically verifies the schedulability of each component of the job with respect to the job's constraints and those of other jobs in the system. These time constraints include those that govern interrupt processing, which allows the MARUTI approach to succeed where tess rigorous approaches do not. The result is that MARUTI applications can be executed in a predictable, deterministic fashion.

A Framework with Proactive Nodes for Scheduling and Optimizing Distributed Embedded Systems

“…Examples of early investigations on the field can be found in [3] and [4], where some of the first solutions applicable to DES were described.…”

An Analysis of Zero-Clairvoyant Scheduling

“…We used lp-solve 6 [Ber95] for all our algorithms. Table (2) details the machine characteristics, while table (3) tabulates our results 7 : Most of the constraints were chosen from the boeing data-set, provided as part of [LTCA89], while some of them were randomly generated. The execution time domain E for most inputs was an axis-parallel hyper-rectangle, although we did use general polyhedra for some constraint sets.…”

Real-Time System Scheduling

“…Threads (processes) are resident inside an object and are not permitted to move outside of that object. The same restriction is seen in the Maruti kernel 49 where the processes and resources required for a specific part of the application are grouped together into a single object. The StarOS kernel 35 restricts processes to exist within a single object also.…”