3. Preemptivity Of Jobs
• Preemptable Job :- Can be suspended and
resumed from the suspention point
• Example :- Computations
• Non-preemptable :- Data transmission
3
4. Criticality Of Jobs
• Criticality of job :- Positive number indicating
how critical the job is.
• Increases with importance of job
• Don’t use the terms priority and weight
4
5. Optional Executions
• If an optional job or optional portion
completes late or is not executed at all, the
system still functions satisfactorily.
• Non-optional job :- Mandatory
5
6. Laxity Type & Laxity Functions
• Laxity type:- indicates whether the job is hard
or soft.
• Hard RT Jobs:- “Better never than late”.
• Soft RT Jobs:- Usefulness decreases gradually.
6
7. Resource Parameters Of Jobs &
Parameters Of Job Resources
• Preemptivity Of Resources
• Resource Graph
7
8. Preemptivity Of Resources
• Describing processors and resources
independently of application Parameter of
resources: Preemptivity.
• Nonpreemptable resource: Each unit is to be
used serially.
8
9. Resource Graph
• Configuration of the resources
• Vertex Ri for every processor or resource Ri in
the system.
• Attributes of the vertex are the parameters of
the resource.
• P- processors, R- for passive resources
• Parameters
– Type
– Number of available units.
9
11. Scheduling Hierarchy
• Task Graph
– Representation of application system.
– Processor time
– Resource requirement
– Timing constraints & dependencies of jobs
• Resource Graph
– Amount of available resources
– Resource attributes
– Usage rules
• Scheduling and resource access-control
algorithms used by the operating system.
11
12. Scheduler & Schedules
• Scheduler:
– implements scheduling algorithms
–Schedules Jobs,
–Allocates Resources.
Example: Processors assignment on jobs (or vice
versa).
• Schedule: Assignment of all system jobs on
available processors produced by the scheduler.
12
13. Valid Schedule
• Every processor assigned to at most one job at
any time
• Every job is assigned at most one processor at
any time.
• No job is scheduled before its release-time.
• Total amount of processor time = execution
time
• Precedence and resource usage constraints
are satisfied.
13
14. Feasibility, Optimality & Performance
Measures
• valid schedule is a feasible schedule if every
job completes by its deadline.
• Hard RTS scheduling algorithm is optimal if
(using) the algorithm (the scheduler) always
produces a feasible schedule if the given set of
jobs has feasible schedules.
• Lateness, tardiness, miss ,loss and invalid
rates.
14