Silberschatz Ch03 Processes

8/11/2019 Silberschatz Ch03 Processes

1/33

Processes


2/33

Chapter 3: Processes

Process Concept Process Scheduling

Operations on Processes

Interprocess Communication


3/33

3.1 Process Concept


4/33

Process Concept

An operating system executes a

variety of programs:

Batch systemjobs

Time-shared systemsuser programs or

tasks

Textbook uses the termsjoband

processalmost interchangeably

Processa program in execution;

process execution must progress insequential fashion

A process includes:

program counter and process registers

stack and heap


5/33

Process State

As a process executes, it changes state

new: The process is being created running: Instructions are being executed

waiting: The process is waiting for some event to

occur (such as an I/O completion or reception of a

signal)

ready: The process is waiting to be assigned to aprocessor

terminated: The process has finished execution


6/33

Process Control Block (PCB)

Information associated with each process Process state

Program counter

CPU registers

CPU scheduling information Memory-management information

Accounting information

I/O status information


7/33

CPU Switch From Process to Process


8/33

Context Switch

When CPU switches to another process(because of an interrupt), the system mustsave the state of the old process and load thesaved state for the new process

Context-switch time is overhead; the systemdoes no useful work while switching

Time dependent on hardware support


9/33

3.2 Process Scheduling


10/33

Process Scheduling Queues

Job queueset of all processes in thesystem

Ready queueset of all processes residing inmain memory, ready and waiting to execute

Device queuesset of processes waiting foran I/O device

Processes migrate among the various queues


11/33

Ready Queue And Various I/O Device Queues


12/33

Representation of Process Scheduling

An interrupt occurs


13/33


14/33

Schedulers (Cont.)

Short-term scheduler is invoked very frequently(milliseconds) (must be fast)

Long-term scheduler is invoked very infrequently(seconds, minutes)(may be slow)

The long-term scheduler controls the degree ofmultiprogramming

Processes can be described as either: I/O-bound processspends more time doing I/O

than computations, many short CPU bursts CPU-bound processspends more time doing

computations; few very long CPU bursts Some systems have no long-term scheduler

Every new process is loaded into memory System stability effected by physical limitation and

self-adjusting nature of the human user


15/33


16/33

Process Creation

Parent process creates children processes,which, in turn create other processes, forming

a tree of processes

Resource sharing options

Parent and children share all resourcesChildren share subset of parents resources

Parent and child share no resources

Execution options

Parent and children execute concurrently

Parent waits until some or all of its children have

terminated


17/33

Process Creation (Cont.)

Address space options Child process is a duplicate of the parent

process (same program and data)

Child process has a new program loaded into it

UNIX example fork()system call creates a new process

exec()system call used after a fork()to replace

the memory space of the process with a new

program


18/33

Process Tree on a typical Solaris System


19/33

C Program Forking Separate Process

int main(void)

{

pid_t processID;

processID = fork(); // Create a process

if (processID < 0)

{ // Error occurred

fprintf(stderr, "Fork failed");

exit(-1);

} // End if

else if (processID == 0)

{ // Inside the child process (no execlp() this time)

printf ("(Child) I am doing something");

} // End else if

else

{ // Inside the parent processprintf("(Parent) I am waiting for PID#%d to finish\n", processID);

wait(NULL);

printf ("\n(Parent) I have finished waiting; the child is done");

exit(0);

} // End else

return 0;

} // End main


20/33

Process Creation


21/33

Process Termination

Process executes last statement and asks theoperating system to terminate it (via exit)

Exit (or return) status value from child is received by theparent (via wait())

Process resources are deallocated by operating system

Parent may terminate execution of children processes(kill() function) Child has exceeded allocated resources

Task assigned to child is no longer required

If parent is exiting Some operating system do not allow child to continue if its

parent terminates

All children terminated - cascading termination


22/33

3.4 Interprocess Communication


23/33

Cooperating Processes

An independentprocess is one that cannot affector be affected by the execution of another process

A cooperatingprocess can affect or be affectedby the execution of another process in the system

Advantages of process cooperation Information sharing (of the same piece of data) Computation speed-up (break a task into smaller

subtasks)

Modularity (dividing up the system functions)

Convenience (to do multiple tasks simultaneously)

Two fundamental models of interprocesscommunication Shared memory (a region of memory is shared)

Message passing (exchange of messages between

processes)


24/33

Communications Models

Message passing Shared memory


25/33

Shared Memory Systems

Shared memory requires communicatingprocesses to establish a region of sharedmemory

Information is exchanged by reading and

writing data in the shared memoryA common paradigm for cooperating

processes is the producer-consumerproblem

Aproducerprocess produces informationthat is consumed by a consumerprocessunbounded-bufferplaces no practical limit

on the size of the buffer

bounded-bufferassumes that there is a

fixed buffer size


26/33

Message-Passing Systems

Mechanism to allow processes to communicate and to synchronize their

actions

No address space needs to be shared; this is particularly useful in a

distributed processing environment (e.g., a chat program)

Message-passing facility provides two operations:

send(message)message size can be fixed or variable

receive(message)

If Pand Qwish to communicate, they need to:

establish a communicationlinkbetween them

exchange messages via send/receive

Logical implementation of communication link

Direct or indirect communication

Synchronous or asynchronous communication

Automatic or explicit buffering


27/33

Implementation Questions

How are links established? Can a link be associated with more than two

processes?

How many links can there be between every

pair of communicating processes? What is the capacity of a link?

Is the size of a message that the link can

accommodate fixed or variable?

Is a link unidirectional or bi-directional?


28/33

Direct Communication

Processes must name each other explicitly: send(P, message)send a message to

process P

receive(Q, message)receive a message from

process Q Properties of communication link

Links are established automatically between

every pair of processes that want to

communicateA link is associated with exactly one pair of

communicating processes

Between each pair there exists exactly one link

The link may be unidirectional, but is usually bi-directional


29/33

Indirect Communication

Messages are directed and received frommailboxes (also referred to as ports) Each mailbox has a unique id

Processes can communicate only if they sharea mailbox send(A, message)send message to mailbox A receive(A, message)receive message from

mailbox A

Properties of communication link

Link is established between a pair ofprocesses only if both have a shared mailbox

A link may be associated with more than twoprocesses

Between each pair of processes, there may be

many different links, with each link


30/33

(continued)

For a shared mailbox, messages arereceived based on the following methods:Allow a link to be associated with at most

two processes

Allow at most one process at a time to

execute a receive() operationAllow the system to select arbitrarily which

process will receive the message (e.g., around robin approach)

Mechanisms provided by the operatingsystem Create a new mailbox

Send and receive messages through themailbox

Destroy a mailbox


31/33

Synchronization

Message passing may be either blocking ornon-blocking

Blockingis considered synchronous

Blocking send has the sender block until the

message is received Blocking receive has the receiver block until

a message is available

Non-blockingis considered asynchronous

Non-blocking send has the sender send themessage and continue

Non-blocking receive has the receiver receive

a valid message or null

When both send() and receive() are blocking,


32/33

Buffering

Whether communication is direct or indirect,messages exchanged by communicating

processes reside in a temporary queue

These queues can be implemented in three

ways:1. Zero capacitythe queue has a maximum

length of zero

- Sender must block until the recipient receives

the message2. Bounded capacitythe queue has a finite

length of n

- Sender must wait if queue is full

3. Unbounded capacitythe queue length is

unlimited


33/33

Documents

Silberschatz Ch03 Processes