Description

A SchedClass Key conveys the authority to execute instructions under the resource allotment of a particular scheduling class. Every process must posess a valid schedule key in order to execute instructions. A general description of the EROS scheduling policy can be found in the Scheduling page of the concepts section.

The implementation described here is a short-term placeholder intended to allow us to get programs running quickly. We will be replacing it completely in the near future.

EROS currently supports three scheduling classes:

• important threads receive a larger share of the processor, and queue ahead of all lower classes.
• normal threads receive a more limited share of the processor, and queue ahead of idle processes
• idle processes run when there is nothing better to do.

The current implementation is in fact a priority scheme, but this will change in the future.

No operations are currently defined on schedule keys.