Free Essay

Cpu Scheduling

In:

Submitted By lilyana
Words 3375
Pages 14
Chapter 5: CPU Scheduling

Operating System Concepts – 8th Edition

Silberschatz, Galvin and Gagne ©2009

Chapter 5: CPU Scheduling
      

Basic Concepts Scheduling Criteria Scheduling Algorithms Thread Scheduling Multiple-Processor Scheduling Operating Systems Examples Algorithm Evaluation

Operating System Concepts – 8th Edition

5.2

Silberschatz, Galvin and Gagne ©2009

Objectives
  

To introduce CPU scheduling, which is the basis for multiprogrammed operating systems To describe various CPU-scheduling algorithms To discuss evaluation criteria for selecting a CPU-scheduling algorithm for a particular system

Operating System Concepts – 8th Edition

5.3

Silberschatz, Galvin and Gagne ©2009

Basic Concepts
  

Maximum CPU utilization obtained with multiprogramming CPU–I/O Burst Cycle – Process execution consists of a cycle of CPU execution and I/O wait CPU burst distribution

Operating System Concepts – 8th Edition

5.4

Silberschatz, Galvin and Gagne ©2009

Alternating Sequence of CPU and I/O Bursts

Operating System Concepts – 8th Edition

5.5

Silberschatz, Galvin and Gagne ©2009

Histogram of CPU-burst Times

Operating System Concepts – 8th Edition

5.6

Silberschatz, Galvin and Gagne ©2009

CPU Scheduler
 

Selects from among the processes in ready queue, and allocates the CPU to one of them


Queue may be ordered in various ways Switches from running to waiting state Switches from running to ready state Switches from waiting to ready Terminates

CPU scheduling decisions may take place when a process: 1. 2. 3.
4.

 

Scheduling under 1 and 4 is nonpreemptive All other scheduling is preemptive
  

Consider access to shared data Consider preemption while in kernel mode Consider interrupts occurring during crucial OS activities

Operating System Concepts – 8th Edition

5.7

Silberschatz, Galvin and Gagne ©2009

Dispatcher


Dispatcher module gives control of the CPU to the process selected by the short-term scheduler; this involves:
  

switching context switching to user mode jumping to the proper location in the user program to restart that program



Dispatch latency – time it takes for the dispatcher to stop one process and start another running

Operating System Concepts – 8th Edition

5.8

Silberschatz, Galvin and Gagne ©2009

Scheduling Criteria
    

CPU utilization – keep the CPU as busy as possible Throughput – # of processes that complete their execution per time unit Turnaround time – amount of time to execute a particular process Waiting time – amount of time a process has been waiting in the ready queue Response time – amount of time it takes from when a request was submitted until the first response is produced, not output (for time-sharing environment)

Operating System Concepts – 8th Edition

5.9

Silberschatz, Galvin and Gagne ©2009

Scheduling Algorithm Optimization Criteria
    

Max CPU utilization Max throughput Min turnaround time Min waiting time Min response time

Operating System Concepts – 8th Edition

5.10

Silberschatz, Galvin and Gagne ©2009

First-Come, First-Served (FCFS) Scheduling
Process Burst Time



P1 24 P2 3 P3 3 Suppose that the processes arrive in the order: P1 , P2 , P3 The Gantt Chart for the schedule is:

P1

P2

P3

0
 

24

27

30

Waiting time for P1 = 0; P2 = 24; P3 = 27 Average waiting time: (0 + 24 + 27)/3 = 17

Operating System Concepts – 8th Edition

5.11

Silberschatz, Galvin and Gagne ©2009

FCFS Scheduling (Cont.)
Suppose that the processes arrive in the order: P2 , P3 , P1


The Gantt chart for the schedule is:

P2

P3

P1

0
   

3

6

30

Waiting time for P1 = 6; P2 = 0; P3 = 3 Average waiting time: (6 + 0 + 3)/3 = 3 Much better than previous case Convoy effect - short process behind long process


Consider one CPU-bound and many I/O-bound processes

Operating System Concepts – 8th Edition

5.12

Silberschatz, Galvin and Gagne ©2009

Shortest-Job-First (SJF) Scheduling


Associate with each process the length of its next CPU burst


Use these lengths to schedule the process with the shortest time



SJF is optimal – gives minimum average waiting time for a given set of processes
 

The difficulty is knowing the length of the next CPU request Could ask the user

Operating System Concepts – 8th Edition

5.13

Silberschatz, Galvin and Gagne ©2009

Example of SJF
ProcessArriva P1 P2 P3 P4


l Time 0.0 2.0 4.0 5.0

Burst Time 6 8 7 3

SJF scheduling chart P4 P1 3 9 P3 P2

0


16

24

Average waiting time = (3 + 16 + 9 + 0) / 4 = 7

Operating System Concepts – 8th Edition

5.14

Silberschatz, Galvin and Gagne ©2009

Determining Length of Next CPU Burst


Can only estimate the length – should be similar to the previous one


Then pick process with shortest predicted next CPU burst



Can be done by using the length of previous CPU bursts, using exponential averaging

1. t n = actual length of n th CPU burst 2. τ n +1 = predicted value for the next CPU burst 3. α , 0 ≤ α ≤ 1 4. Define :
 

Commonly, α set to ½ Preemptive version called shortest-remaining-time-first

τ n =1 = α t n + (1 − α )τ n .

Operating System Concepts – 8th Edition

5.15

Silberschatz, Galvin and Gagne ©2009

Prediction of the Length of the Next CPU Burst

Operating System Concepts – 8th Edition

5.16

Silberschatz, Galvin and Gagne ©2009

Examples of Exponential Averaging


α =0
 

τn+1 = τn Recent history does not count



α =1 τn+1 = α tn  Only the actual last CPU burst counts If we expand the formula, we get: τn+1 = α tn+(1 - α)α tn -1 + … +(1 - α )j α tn -j + … +(1 - α )n +1 τ0






Since both α and (1 - α) are less than or equal to 1, each successive term has less weight than its predecessor

Operating System Concepts – 8th Edition

5.17

Silberschatz, Galvin and Gagne ©2009

Example of Shortest-remaining-time-first


Now we add the concepts of varying arrival times and preemption to the analysis ProcessA P1 P2 P3 P4 arri Arrival TimeT 0 1 2 3 Burst Time 8 4 9 5



Preemptive SJF Gantt Chart

P1

P2

P4

P1

P3

0


1

5

10

17

26

Average waiting time = [(10-1)+(1-1)+(17-2)+5-3)]/4 = 26/4 = 6.5 msec

Operating System Concepts – 8th Edition

5.18

Silberschatz, Galvin and Gagne ©2009

Priority Scheduling
 

A priority number (integer) is associated with each process The CPU is allocated to the process with the highest priority (smallest integer ≡ highest priority)
 

Preemptive Nonpreemptive

  

SJF is priority scheduling where priority is the inverse of predicted next CPU burst time Problem ≡ Starvation – low priority processes may never execute Solution ≡ Aging – as time progresses increase the priority of the process

Operating System Concepts – 8th Edition

5.19

Silberschatz, Galvin and Gagne ©2009

Example of Priority Scheduling
ProcessA P1 P2 P3 P4 P5


arri Burst TimeT 10 1 2 1 5

Priority 3 1 4 5 2

Priority scheduling Gantt Chart P2 P5 P1 P3 P4

0


1

6

16

18

19

Average waiting time = 8.2 msec

Operating System Concepts – 8th Edition

5.20

Silberschatz, Galvin and Gagne ©2009

Round Robin (RR)
   

Each process gets a small unit of CPU time (time quantum q), usually 10-100 milliseconds. After this time has elapsed, the process is preempted and added to the end of the ready queue. If there are n processes in the ready queue and the time quantum is q, then each process gets 1/n of the CPU time in chunks of at most q time units at once. No process waits more than (n-1)q time units. Timer interrupts every quantum to schedule next process Performance
 

q large ⇒ FIFO q small ⇒ q must be large with respect to context switch, otherwise overhead is too high

Operating System Concepts – 8th Edition

5.21

Silberschatz, Galvin and Gagne ©2009

Example of RR with Time Quantum = 4
Process P1 P2 P3


Burst Time 24 3 3

The Gantt chart is:

P1 0
  

P2 4 7

P3 10

P1 14

P1 18

P1 22

P1 26

P1 30

Typically, higher average turnaround than SJF, but better response q should be large compared to context switch time q usually 10ms to 100ms, context switch < 10 usec

Operating System Concepts – 8th Edition

5.22

Silberschatz, Galvin and Gagne ©2009

Time Quantum and Context Switch Time

Operating System Concepts – 8th Edition

5.23

Silberschatz, Galvin and Gagne ©2009

Turnaround Time Varies With The Time Quantum

80% of CPU bursts should be shorter than q

Operating System Concepts – 8th Edition

5.24

Silberschatz, Galvin and Gagne ©2009

Multilevel Queue


Ready queue is partitioned into separate queues, eg:
 

foreground (interactive) background (batch)

 

Process permanently in a given queue Each queue has its own scheduling algorithm:
 

foreground – RR background – FCFS



Scheduling must be done between the queues:
  

Fixed priority scheduling; (i.e., serve all from foreground then from background). Possibility of starvation. Time slice – each queue gets a certain amount of CPU time which it can schedule amongst its processes; i.e., 80% to foreground in RR 20% to background in FCFS

Operating System Concepts – 8th Edition

5.25

Silberschatz, Galvin and Gagne ©2009

Multilevel Queue Scheduling

Operating System Concepts – 8th Edition

5.26

Silberschatz, Galvin and Gagne ©2009

Multilevel Feedback Queue
 

A process can move between the various queues; aging can be implemented this way Multilevel-feedback-queue scheduler defined by the following parameters:
    

number of queues scheduling algorithms for each queue method used to determine when to upgrade a process method used to determine when to demote a process method used to determine which queue a process will enter when that process needs service

Operating System Concepts – 8th Edition

5.27

Silberschatz, Galvin and Gagne ©2009

Example of Multilevel Feedback Queue


Three queues:
  

Q0 – RR with time quantum 8 milliseconds Q1 – RR time quantum 16 milliseconds Q2 – FCFS



Scheduling


A new job enters queue Q0 which is served FCFS
 

When it gains CPU, job receives 8 milliseconds If it does not finish in 8 milliseconds, job is moved to queue Q1 If it still does not complete, it is preempted and moved to queue Q2



At Q1 job is again served FCFS and receives 16 additional milliseconds


Operating System Concepts – 8th Edition

5.28

Silberschatz, Galvin and Gagne ©2009

Multilevel Feedback Queues

Operating System Concepts – 8th Edition

5.29

Silberschatz, Galvin and Gagne ©2009

Thread Scheduling
  

Distinction between user-level and kernel-level threads When threads supported, threads scheduled, not processes Many-to-one and many-to-many models, thread library schedules user-level threads to run on LWP
 

Known as process-contention scope (PCS) since scheduling competition is within the process Typically done via priority set by programmer



Kernel thread scheduled onto available CPU is system-contention scope (SCS) – competition among all threads in system

Operating System Concepts – 8th Edition

5.30

Silberschatz, Galvin and Gagne ©2009

Pthread Scheduling


API allows specifying either PCS or SCS during thread creation
 

PTHREAD_SCOPE_PROCESS schedules threads using PCS scheduling PTHREAD_SCOPE_SYSTEM schedules threads using SCS scheduling



Can be limited by OS – Linux and Mac OS X only allow PTHREAD_SCOPE_SYSTEM

Operating System Concepts – 8th Edition

5.31

Silberschatz, Galvin and Gagne ©2009

Pthread Scheduling API
#include #include #define NUM THREADS 5 int main(int argc, char *argv[]) { int i; pthread t tid[NUM THREADS]; pthread attr t attr; /* get the default attributes */ pthread attr init(&attr); /* set the scheduling algorithm to PROCESS or SYSTEM */ pthread attr setscope(&attr, PTHREAD SCOPE SYSTEM); /* set the scheduling policy - FIFO, RT, or OTHER */ pthread attr setschedpolicy(&attr, SCHED OTHER); /* create the threads */ for (i = 0; i < NUM THREADS; i++) pthread create(&tid[i],&attr,runner,NULL);

Operating System Concepts – 8th Edition

5.32

Silberschatz, Galvin and Gagne ©2009

Pthread Scheduling API
/* now join on each thread */ for (i = 0; i < NUM THREADS; i++) pthread join(tid[i], NULL); } /* Each thread will begin control in this function */ void *runner(void *param) { printf("I am a thread\n"); pthread exit(0); }

Operating System Concepts – 8th Edition

5.33

Silberschatz, Galvin and Gagne ©2009

Multiple-Processor Scheduling
  

CPU scheduling more complex when multiple CPUs are available Homogeneous processors within a multiprocessor Asymmetric multiprocessing – only one processor accesses the system data structures, alleviating the need for data sharing Symmetric multiprocessing (SMP) – each processor is self-scheduling, all processes in common ready queue, or each has its own private queue of ready processes




Currently, most common



Processor affinity – process has affinity for processor on which it is currently running
  

soft affinity hard affinity Variations including processor sets

Operating System Concepts – 8th Edition

5.34

Silberschatz, Galvin and Gagne ©2009

NUMA and CPU Scheduling

Note that memory-placement algorithms can also consider affinity

Operating System Concepts – 8th Edition

5.35

Silberschatz, Galvin and Gagne ©2009

Multicore Processors
  

Recent trend to place multiple processor cores on same physical chip Faster and consumes less power Multiple threads per core also growing


Takes advantage of memory stall to make progress on another thread while memory retrieve happens

Operating System Concepts – 8th Edition

5.36

Silberschatz, Galvin and Gagne ©2009

Multithreaded Multicore System

Operating System Concepts – 8th Edition

5.37

Silberschatz, Galvin and Gagne ©2009

Virtualization and Scheduling
 

Virtualization software schedules multiple guests onto CPU(s) Each guest doing its own scheduling
  

Not knowing it doesn’t own the CPUs Can result in poor response time Can effect time-of-day clocks in guests



Can undo good scheduling algorithm efforts of guests

Operating System Concepts – 8th Edition

5.38

Silberschatz, Galvin and Gagne ©2009

Operating System Examples
  

Solaris scheduling Windows XP scheduling Linux scheduling

Operating System Concepts – 8th Edition

5.39

Silberschatz, Galvin and Gagne ©2009

Solaris
 

Priority-based scheduling Six classes available
     

Time sharing (default) Interactive Real time System Fair Share Fixed priority

  

Given thread can be in one class at a time Each class has its own scheduling algorithm Time sharing is multi-level feedback queue


Loadable table configurable by sysadmin

Operating System Concepts – 8th Edition

5.40

Silberschatz, Galvin and Gagne ©2009

Solaris Dispatch Table

Operating System Concepts – 8th Edition

5.41

Silberschatz, Galvin and Gagne ©2009

Solaris Scheduling

Operating System Concepts – 8th Edition

5.42

Silberschatz, Galvin and Gagne ©2009

Solaris Scheduling (Cont.)


Scheduler converts class-specific priorities into a per-thread global priority
  

Thread with highest priority runs next Runs until (1) blocks, (2) uses time slice, (3) preempted by higher-priority thread Multiple threads at same priority selected via RR

Operating System Concepts – 8th Edition

5.43

Silberschatz, Galvin and Gagne ©2009

Windows Scheduling
         

Windows uses priority-based preemptive scheduling Highest-priority thread runs next Dispatcher is scheduler Thread runs until (1) blocks, (2) uses time slice, (3) preempted by higher-priority thread Real-time threads can preempt non-real-time 32-level priority scheme Variable class is 1-15, real-time class is 16-31 Priority 0 is memory-management thread Queue for each priority If no run-able thread, runs idle thread

Operating System Concepts – 8th Edition

5.44

Silberschatz, Galvin and Gagne ©2009

Windows Priority Classes


Win32 API identifies several priority classes to which a process can belong


REALTIME_PRIORITY_CLASS, HIGH_PRIORITY_CLASS, ABOVE_NORMAL_PRIORITY_CLASS,NORMAL_PRIORITY_CLASS, BELOW_NORMAL_PRIORITY_CLASS, IDLE_PRIORITY_CLASS All are variable except REALTIME TIME_CRITICAL, HIGHEST, ABOVE_NORMAL, NORMAL, BELOW_NORMAL, LOWEST, IDLE



     

A thread within a given priority class has a relative priority


Priority class and relative priority combine to give numeric priority Base priority is NORMAL within the class If quantum expires, priority lowered, but never below base If wait occurs, priority boosted depending on what was waited for Foreground window given 3x priority boost

Operating System Concepts – 8th Edition

5.45

Silberschatz, Galvin and Gagne ©2009

Windows XP Priorities

Operating System Concepts – 8th Edition

5.46

Silberschatz, Galvin and Gagne ©2009

Linux Scheduling
        

Constant order O(1) scheduling time Preemptive, priority based Two priority ranges: time-sharing and real-time Real-time range from 0 to 99 and nice value from 100 to 140 Map into global priority with numerically lower values indicating higher priority Higher priority gets larger q Task run-able as long as time left in time slice (active) If no time left (expired), not run-able until all other tasks use their slices All run-able tasks tracked in per-CPU runqueue data structure  Two priority arrays (active, expired)  Tasks indexed by priority  When no more active, arrays are exchanged

Operating System Concepts – 8th Edition

5.47

Silberschatz, Galvin and Gagne ©2009

Linux Scheduling (Cont.)
 

Real-time scheduling according to POSIX.1b


Real-time tasks have static priorities Interactivity of task determines plus or minus


All other tasks dynamic based on nice value plus or minus 5


More interactive -> more minus

 

Priority recalculated when task expired This exchanging arrays implements adjusted priorities

Operating System Concepts – 8th Edition

5.48

Silberschatz, Galvin and Gagne ©2009

Priorities and Time-slice length

Operating System Concepts – 8th Edition

5.49

Silberschatz, Galvin and Gagne ©2009

List of Tasks Indexed According to Priorities

Operating System Concepts – 8th Edition

5.50

Silberschatz, Galvin and Gagne ©2009

Algorithm Evaluation
  

How to select CPU-scheduling algorithm for an OS? Determine criteria, then evaluate algorithms Deterministic modeling
 

Type of analytic evaluation Takes a particular predetermined workload and defines the performance of each algorithm for that workload

Operating System Concepts – 8th Edition

5.51

Silberschatz, Galvin and Gagne ©2009

Queueing Models


Describes the arrival of processes, and CPU and I/O bursts probabilistically
 

Commonly exponential, and described by mean Computes average throughput, utilization, waiting time, etc Knowing arrival rates and service rates Computes utilization, average queue length, average wait time, etc



Computer system described as network of servers, each with queue of waiting processes
 

Operating System Concepts – 8th Edition

5.52

Silberschatz, Galvin and Gagne ©2009

Little’s Formula
   

n = average queue length W = average waiting time in queue λ = average arrival rate into queue Little’s law – in steady state, processes leaving queue must equal processes arriving, thus n=λxW


Valid for any scheduling algorithm and arrival distribution



For example, if on average 7 processes arrive per second, and normally 14 processes in queue, then average wait time per process = 2 seconds

Operating System Concepts – 8th Edition

5.53

Silberschatz, Galvin and Gagne ©2009

Simulations
 

Queueing models limited Simulations more accurate
   

Programmed model of computer system Clock is a variable Gather statistics indicating algorithm performance Data to drive simulation gathered via
  

Random number generator according to probabilities Distributions defined mathematically or empirically Trace tapes record sequences of real events in real systems

Operating System Concepts – 8th Edition

5.54

Silberschatz, Galvin and Gagne ©2009

Evaluation of CPU Schedulers by Simulation

Operating System Concepts – 8th Edition

5.55

Silberschatz, Galvin and Gagne ©2009

Implementation
 Even simulations have limited accuracy


Just implement new scheduler and test in real systems
 

High cost, high risk Environments vary

  

Most flexible schedulers can be modified per-site or per-system Or APIs to modify priorities But again environments vary

Operating System Concepts – 8th Edition

5.56

Silberschatz, Galvin and Gagne ©2009

End of Chapter 5

Operating System Concepts – 8th Edition

Silberschatz, Galvin and Gagne ©2009

5.08

Operating System Concepts – 8th Edition

5.58

Silberschatz, Galvin and Gagne ©2009

In-5.7

Operating System Concepts – 8th Edition

5.59

Silberschatz, Galvin and Gagne ©2009

In-5.8

Operating System Concepts – 8th Edition

5.60

Silberschatz, Galvin and Gagne ©2009

In-5.9

Operating System Concepts – 8th Edition

5.61

Silberschatz, Galvin and Gagne ©2009

Dispatch Latency

Operating System Concepts – 8th Edition

5.62

Silberschatz, Galvin and Gagne ©2009

Java Thread Scheduling


JVM Uses a Preemptive, Priority-Based Scheduling Algorithm



FIFO Queue is Used if There Are Multiple Threads With the Same Priority

Operating System Concepts – 8th Edition

5.63

Silberschatz, Galvin and Gagne ©2009

Java Thread Scheduling (Cont.)
JVM Schedules a Thread to Run When:
1. 2.

The Currently Running Thread Exits the Runnable State A Higher Priority Thread Enters the Runnable State

* Note – the JVM Does Not Specify Whether Threads are Time-Sliced or Not

Operating System Concepts – 8th Edition

5.64

Silberschatz, Galvin and Gagne ©2009

Time-Slicing
Since the JVM Doesn’t Ensure Time-Slicing, the yield() Method May Be Used: while (true) { // perform CPU-intensive task ... Thread.yield(); } This Yields Control to Another Thread of Equal Priority

Operating System Concepts – 8th Edition

5.65

Silberschatz, Galvin and Gagne ©2009

Thread Priorities
Priority Thread.MIN_PRIORITY Thread.MAX_PRIORITY Thread.NORM_PRIORITY Comment Minimum Thread Priority Maximum Thread Priority Default Thread Priority

Priorities May Be Set Using setPriority() method: setPriority(Thread.NORM_PRIORITY + 2);

Operating System Concepts – 8th Edition

5.66

Silberschatz, Galvin and Gagne ©2009

Solaris 2 Scheduling

Operating System Concepts – 8th Edition

5.67

Silberschatz, Galvin and Gagne ©2009

Similar Documents

Free Essay

Cpu Scheduling

...CPU SCHEDULINGCPU scheduling in UNIX is designed to benefit interactive processes. Processes are given small CPU time slices by a priority algorithm that reduces to round-robin scheduling for CPU-bound jobs.The scheduler on UNIX system belongs to the general class of operating system schedulers known as round robin with multilevel feedback which means that the kernel allocates the CPU time to a process for small time slice, preempts a process that exceeds its time slice and feed it back into one of several priority queues. A process may need much iteration through the "feedback loop" before it finishes. When kernel does a context switch and restores the context of a process. The process resumes execution from the point where it had been suspended.Each process table entry contains a priority field. There is a process table for each process which contains a priority field for process scheduling. The priority of a process is lower if they have recently used the CPU and vice versa.The more CPU time a process accumulates, the lower (more positive) its priority becomes, and vice versa, so there is negative feedback in CPU scheduling and it is difficult for a single process to take all the CPU time. Process aging is employed to prevent starvation.Older UNIX systems used a 1-second quantum for the round- robin scheduling. 4.33SD reschedules processes every 0.1 second and recomputed priorities every second. The round-robin scheduling is accomplished by the -time-out mechanism, which tells...

Words: 2136 - Pages: 9

Free Essay

Cpu Scheduling Algorithms Simulation

...FINAL YEAR PROJECT On DESIGNING A SIMULATOR TO IMPLEMENT A JOB SCHEDULER BASED ON DIFFERENT POPULAR CPU SCHEDULING ALGORITHMS Submitted as partial fulfillment for the award of BACHELOR OF TECHNOLOGY Session 2014-15 In Computer Science & Engineering Under the guidance of Mr.MrinmoySen By AnanyaDas(11/CS/15, ananyadas092@gmail.com, +919681851782) AnshumanMahanty(11/CS/23, anshumanmahanty1@gmail.com, +917501169824) SayaniBanerjee(11/CS/93, sayanibanerjee.1@gmail.com, +919046422003) HALDIA INSTITUTE OF TECHNOLOGY, HALDIA CERTIFICATE This is to certify that the final year project (CS792) on ‘Designing a Simulator implementing job scheduler based on different popular CPU scheduling algorithms’ has been completed and submitted successfully by the project members Ananya Das (11/CS/15), Anshuman Mahanty (11/CS/23) and Sayani Banerjee (11/CS/93). ------------------------- -------------------------------- --------------------------- Mr. Tarun Kumar Ghosh Mr. Sourav Mandal, Mr. Mrinmoy Sen Head of the Department, Convenor, Asst. Prof., Project Mentor, Asst. Prof., Computer Science & Engg. Project Evaluation Committee Department of CSE ACKNOWLEDGEMENTS We use this opportunity to express our gratitude to everyone who has supported us through the ongoing course of this final year project. The project owes its success not just...

Words: 6989 - Pages: 28

Premium Essay

Nt1330 Unit 1 Term Paper

...Q1. Name some events in operating system which are responsible to allocate resources and to control user programs to prevent errors. These resources include time, power, hardware, etc... that controls the operation of the application programs to prevent errors. Q2.Consider a well-known reputed university having thousands of students enrolled, at the end of semester each student must have a semester end report generated by computer. Each report card needs same resources to execute. Being a student of operating system, you know operating system responsibility is to schedule the job. In your perspective, which environment will be suitable for given scenario to increase CPU utilization? Support your answers with 2-3 reasons. Ans: FCFS is used...

Words: 1247 - Pages: 5

Free Essay

Operating Systems

...queue I/O queue CPU CPU READY QUEUE READY QUEUE PROCESS I/OO I/OO Queuing Diagram I/OO I/OO I/OO I/OO Long term scheduler (job scheduler) – decides which jobs are admitted to the system for processing (brings jobs to the ready state). Short term scheduler (CPU scheduler) – selects which job from the ready queue would be the next one to get to the CPU. Non-preemptive vs. Preemptive * Jobs are expected one at a time until - an active job will be completion. Once a job is selected it interrupted and placed back Is serviced even if a higher priority job in the ready queue if a higher Arrives priority job requires service. 1.) First Come First Served (FCFS) - executes jobs in their order of arrival (the job that comes first will get to the CPU first). - implemented easily using a first in first out (FIFO) queue. - FCFS is non-preemptive. - PROBLEM: the average turnaround times and waiting times are HIGH. 2.) Shortest Job First (SJF) – the job with the shortest estimated time is the next one to receive service. - cannot be implemented at the short term scheduling level since there is no way to know the length of the next CPU burst. - can be implemented at the long term scheduling level by asking users to estimate their job time limit. - can be preemptive or non-preemptive. - SJF gives the minimum average waiting time. - PROBLEM: long jobs may never get to execute. 3.) Priority Scheduling: the highest priority...

Words: 906 - Pages: 4

Free Essay

Os Study Guide

...operation of the computer system. To prevent user programs from interfering with the proper operation of the system, the hardware has two modes: user mode and kernel mode. Various instructions (such as I/0 instructions and halt instructions) are privileged and can be executed only in kernel mode. 2.) Kernel Mode In Kernel mode, the executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. Kernel mode is generally reserved for the lowest-level, most trusted functions of the operating system. Crashes in kernel mode are catastrophic; they will halt the entire PC. 3.) User Mode In User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode. -services it provides? 1.) CPU moves data from/to...

Words: 2427 - Pages: 10

Free Essay

Swear as Mechanism to Pain

...the operating system is the kernel. The kernel is a control program that functions in privileged state that allows all hardware instructions to be executed. It reacts to interrupts from external devices and to service requests and traps from processes. The kernel creates and terminates processes and responds to requests for service. Operating systems are resource managers. The main resource is computer hardware in the form of processors, storage, input/output devices, communication devices, and data. Operating system functions include: • Implementing the user interface. • Sharing hardware among users. • Allowing users to share data among themselves. • Preventing users from interfering with one another. • Scheduling resources among users. • Facilitating input/output. • Recovering from errors. • Accounting for resource usage. • Facilitating parallel operations. • Organizing data for secure and rapid access. • Handling network communications. Processes run applications, which are linked together with libraries that perform standard services. The kernel supports the processes by providing a path to the peripheral devices. The kernel responds to service...

Words: 2421 - Pages: 10

Free Essay

Mcq Comupter

...1. |Round robin scheduling is essentially the preemptive version of __________fsecond | |  | | |1) |FIFO | |2) |Shortest job first | |3) |Shortest remaining | |4) |Longest time first | | |Correct Answer: FIFO   [hide] | | | |Marks: 1 | | | | | | | | | | |2. |A page fault occurs | |  | |1) |when the page is not in the memory | |2) |when the page is in the memory | |3) |when...

Words: 2016 - Pages: 9

Free Essay

Srs Woow

...بسم الله الرحمن الرحيم Name: -------------------------------- Group:---- Level:------- Major:------------- |المملكة العربية السعودية |[pic] |KINGDOM OF SAUDI ARABIA | |وزارة التعليم العالي | |Ministry of Higher Education | |جامعة الإمام محمد بن سعود الإسلامية | |Al-Imam Muhammad Ibn Saud Islamic University | |كلية علوم الحاسب والمعلومات | |College of Computer & Information Sciences | CS231: Operating Systems 1st Mid-Term Exam 2nd semester of 1430/1431 Exam Duration: 1:30H Marks: out of 20 I. Multiple choices [6 Marks, 1 for each]: 1. Which of the following is not shared by different threads of the same process? a. Global variables b. Program counter c. Open files d. None of the above 2. Which of the following process state transitions is NOT correct? a. RUNNIG to READY b. READY to RUNNIG c. WAITING to RUNNING d. WAITING to READY 3. Which of the following programming examples, multithreading provides better performance than a single-threaded solution? a. A web server that responds clients service requests b. A web browser that can process...

Words: 693 - Pages: 3

Premium Essay

Os Final

...system has 16 drives and each process can have 4 drives. What is the maximum number of n that the system is deadlock free. [5] Given the sequence below which processes will cause a page fault. (for FIFO – LRU) Write a loop that would create 10 child processes. (No more than 10). If a file is shared by two processes, can have read-only and the other read-write access. If yes how, if not what prevent it. What are some of the security features in UNIX or NT. How does NTFS directory system work. How does UNIX directory system work. Pick a Unix UNIX process scheduler and explain how (not why or when) it favors I/O bound processes to CPU bound processes. Explain and compare I/O software (programmed, interrupt, DMA). What is the problem with RAID4 and explain how RAID5 solves the problem. Disk arm scheduling algorithms readuce read time but what does Linux additionally do. How does Workingset Clock algorithm work. If seektime is 8msec and each track is 160KB. What is the access time to read 4KB. Couffman listed four requirements for a deadlock. Describe fourth one and how to prevent it. What are the advantages of inverted page tables. What is a soft link. Implement soft link and hard links. What are the advantages of FAT32 to FAT16. Readers writes problem. Why doesn’t the code work. Write a better...

Words: 278 - Pages: 2

Free Essay

How Multithreading Works in a Server

...for a service, the server dispatcher creates multiple threads in one server that can be assigned to various client requests simultaneously. Each thread is associated with a separate context or request to the server. This feature is useful in both conversational and RPC servers which otherwise may stay idle waiting for the client side of a conversation. iii. Completion phase- When the application is shut down or stopped, the server performs any termination processing that is necessary such as closing a resource manager. 2. Advantages and Disadvantages of implementing multithreading As user space threads * Switching threads is faster when thread management is done in user space. * Fast thread switching. * Fast thread scheduling. * A multithreaded program operates faster on computer systems that have multiple CPU’s with multiple cores. * A multithreaded application remains responsive to input. This makes it possible for the application to remain responsive to user input while executing tasks. * Superior application responsiveness. If...

Words: 853 - Pages: 4

Free Essay

Women Entrepreneurship

...Chapter 6: CPU Scheduling • • • Basic Concepts Scheduling Criteria Scheduling Algorithms Operating System Concepts 6.1 Basic Concepts • Maximum CPU utilization obtained with multiprogramming. • CPU–I/O Burst Cycle – Process execution consists of a cycle of CPU execution and I/O wait. – Example: Alternating Sequence of CPU And I/O Bursts – In an I/O – bound program would have many very short CPU bursts. – In a CPU – bound program would have a few very long CPU bursts. Operating System Concepts 6.2 1 CPU Scheduler • The CPU scheduler (short-term scheduler) selects from among the processes in memory that are ready to execute, and allocates the CPU to one of them. • A ready queue may be implemented as a FIFO queue, priority queue, a tree, or an unordered linked list. • CPU scheduling decisions may take place when a process: 1. Switches from running to waiting state (ex., I/O request). 2. Switches from running to ready state (ex., Interrupts occur). 3. Switches from waiting to ready state (ex., Completion of I/O). 4. Terminates. • Scheduling under 1 and 4 is nonpreemptive; otherwise is called preemptive. • Under nonpreemptive scheduling, once the CPU has been allocated to a process, the process keeps the CPU until it releases the CPU either by terminating or by switching to the waiting state. Operating System Concepts 6.3 Dispatcher • Dispatcher module gives control of the CPU to the process selected by the short-term scheduler;...

Words: 1887 - Pages: 8

Premium Essay

Cloud Compution

...resources are not equally distributed then this will result in resource wastage. The cloud computing platform guarantees subscribers that it sticks to the service level agreement (SLA) by providing resources as service and by needs based on the broker policy[4]. So in order to get maximum benefit from cloud computing there is need to dynamically balance the load among servers and improve utilization of resources. There are still some areas that are needed to be focused on in cloud computing.  Resource Management  Task Scheduling The task scheduling goals of Cloud computing is provide optimal tasks scheduling for users, and provide the entire cloud system throughput and QoS at the same time. Scheduling is the process of allocating tasks to available resources on the basis of tasks need [5].The main purpose for scheduling is to maximize the utilization of resources. Following are the needs of job scheduling in cloud computing: CPU utilization – keep the CPU as busy as possible (from 0% to 100%) Throughput – # of processes that complete their execution per time unit Turnaround time – amount of time to execute a particular Process Waiting time – amount of time a process has been waiting in the ready queue...

Words: 2467 - Pages: 10

Free Essay

Demo Script

...Walkthrough 10 Segment #1: Scaling-Up Windows Azure Applications using a Single Instance 10 Segment #2: Scaling-Out Windows Azure Applications using Multiple instances 17 Summary 24 * Overview This demo highlights how to scale-up Web Applications on Windows Azure, using the .NET Task Parallel Library (TPL) classes from .NET Framework 4.0. This library efficiently utilizes multiple processors within Windows Azure roles, where the size of the Virtual Machine instance is greater than Small (i.e. where there are multiple processors available). Additionally, the demo shows how to scale-out applications taking advantage of Technical Computing across multiple role instances, using a Job scheduling algorithm. The work is distributed to all the available instances, maximizing the CPU processing of each. Travelling Salesman demo is using a “genetic” algorithm to quickly solve the problem that would ordinarily require very many conventional interactions to solve. The problem and its real–life applications are widely documented (for example, see http://www.tsp.gatech.edu/index.html). The algorithm used in this demo was taken from http://www.heatonresearch.com/online/introduction–neural–networks–cs–edition–2/chapter–6 which explains that the number of steps to solve a problem with N cities is N! (N factorial) (N * (N–1) * (N–2) *… * 2 * 1): Number of Cities | Number of Steps | 1 | 1 | 2 | 1 | 3 | 6 | 4 | 24 | 5 | 120 | 6 | 720 | 7 | 5,040 | 8 | 40,320 | 9...

Words: 3071 - Pages: 13

Free Essay

Business

...US006785889B1 (12) United States Patent Williams (10) Patent N0.: US 6 9 785 9 889 B1 (45) Date of Patent: Aug. 31, 2004 (54) SYSTEM AND METHOD FOR SCHEDULING BANDWIDTH RESOURCES USINGA KALMAN ESTIMATOR WITH ACTIVE FEEDBACK 6,003,062 A * 12/1999 Greenberg et a1. ........ .. 709/104 6,105,053 A * 6,189,022 B1 * 6,263,358 B1 * 8/2000 Kimmel et a1. ..... .. 2/2001 Binns ............. .. 7/2001 Lee et a1. .... .. 709/105 709/100 .. 709/100 Inventor: Peter Williams, * Cited examiner (73) Assignee: Aurema, Inc., Cupertino, CA (US) _ _ _ _ Primary Examiner—Jack B. Harvey ( * ) Notice: SubJect to any disclaimer,~ the term of this Patent 15 extended or adlusted under 35 U'S'C' 154(k)) by 816 days‘ Assistant Examiner_Hai V_ Nguyen (74) Attorney, Agent, or Firm—Michael Hetherington; Nick Ulman; Woodside IP Group (21) Appl. N0.: 09/596,026 (22) Filed: (51) Int C17 (52) U ' ' (57) G06F 9/00 709040 ’ ’ 718/106’ ABSTRACT Jun. 15, 2000 A community of collaborative software agents Works together in a domain to provide functionality such as pro vision of communications services or control of a chemical process. A scheduler is built into each collaborative agent Ci """""""""""" ' """"""""""" " (58) (56) Field of Search """"""""" ’ 709/104 229 718/104; 106’ ’ Which schedules tasks allocated to that particular agent and tasks sub-allocated by the agent. The scheduler has a mecha nism for over-booking...

Words: 10191 - Pages: 41

Free Essay

Positrol Workholding

...|To: |Positrol Workholding | |From: | | |CC: | | |Date: | | |Re: |Job Process Scheduling | | | | Introduction The difference in the job process scheduling will be measured based on table 1 that was given. We are comparing the differences between First Come, First Served (FCFS), Shortest Operating Time (SOT) and Earliest Due Date (EDD) to find which sequencing rule may work the best. Highlights Lateness: The findings (SOT) had the best average of lateness (-3.8), but would still have 3 jobs come up short. On the other hand (EDD) had a slightly lower average at (-2.1), but had no jobs arrive late. With that being said both of these alternative had better averages than the (FCFS) method that positrol workholding is currently using. Jobs: To have the best efficiency and make sure the customers are happy, most jobs should be completed on time which is not the case for the methods (FCFS) and (SOT). They both would have 3 late jobs, whereas (EDD) method would have 0 late jobs, meaning they would all be completed on time. Flow Time: The last...

Words: 1183 - Pages: 5