{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

CSC 7103 20091020 - Updated

CSC 7103 20091020 - Updated - CSC 7103 Chapter 5 Process...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Background image of page 2
Background image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: CSC 7103 10/20/2009 Chapter 5 Process and communication system models Figure 5.5 in textbook List scheduling — no processor remains idle (similar to greedy algorithm). Figure I —- Sample list scheduling Figure 2 — Sample list scheduling + communication costs Page i of 3 CSC 7103 10/20/2009 ELS — Extended list scheduling The goal is to schedule the process that can be executed first. Figure 3 m ELS example "' i ' 5/}; ” a! c .l/ _ .. ll 0“: l V (a? :11 L1 l/Ei l7, “1 [\‘5 (”I ”B ml ‘3 l 5 5 ill ETF — earliest task first Figure 4 — E T F example Page 2 of3 CSC 7103 10/20/2009 Page 3 of 3 SKIP Bokari’s Algorithm Understand the concepts around Figure 5.9 in the textbook. Real Time Scheduling Section 5.5 All processes have deadlines. Delay jitter is the variance in the delay of running a task. Earliest deadline first is a very popular algorithm. This is very similar to earliest task first. In aperiodic systems tasks can appear at any time. In periodic systems tasks appear at periodical/scheduled intervals. In periodic systems, you cannot have more than one instance of the same job running at a time (or you have failed to meet your deadline). 1n real-time systems, the load must stay < 1 or tasks will not complete in time. Rate monotonic Pre—emption is allowed. Without pre-emption, it is possible for task deadlines not to he met because one process might hold the processor causing another job not to complete in time Rate monotonic scheduling relies on the following assumptions: 1. Tasks are periodic and Ti is the period for task ti 2. Tasks do not communicate with each other 3. Tasks are scheduled according to priority, and task priorities are fixed (static priority scheduling) (Ci, Ti) => (CPU time, period) Then 3 tasks (1,4) (3,9) and (1,2) then priorities from highest to lowest are (1,2), (1,4), (3,9) 1) Given a set of tasks how do we determine if the jobs can be run in a feasible manner? 2) Is this optimal? Is the scheme cannot be scheduled, is there another algorithm that can be used to schedule the tasks? ...
View Full Document

{[ snackBarMessage ]}