©2009 Operačné systémy Procesy. 3.2 ©2009 Operačné systémy Process in Memory.

Presentation on theme: "©2009 Operačné systémy Procesy. 3.2 ©2009 Operačné systémy Process in Memory."— Presentation transcript:

1 ©2009 Operačné systémy Procesy

2 3.2 ©2009 Operačné systémy Process in Memory

3 3.3 ©2009 Operačné systémy Diagram of Process State

4 3.4 ©2009 Operačné systémy Process Control Block (PCB)

5 3.5 ©2009 Operačné systémy CPU Switch From Process to Process

6 3.6 ©2009 Operačné systémy Ready Queue And Various I/O Device Queues

7 3.7 ©2009 Operačné systémy Representation of Process Scheduling

8 3.8 ©2009 Operačné systémy Addition of Medium Term Scheduling

9 3.9 ©2009 Operačné systémy Process Creation

10 3.10 ©2009 Operačné systémy C Program Forking Separate Process int main() { pid_t pid; /* fork another process */ pid = fork(); if (pid < 0) { /* error occurred */ fprintf(stderr, "Fork Failed"); exit(-1); } else if (pid == 0) { /* child process */ execlp("/bin/ls", "ls", NULL); } else { /* parent process */ /* parent will wait for the child to complete */ wait (NULL); printf ("Child Complete"); exit(0); }

11 3.11 ©2009 Operačné systémy A tree of processes on a typical Solaris

12 3.12 ©2009 Operačné systémy Interprocess Communication Processes within a system may be independent or cooperating Cooperating process can affect or be affected by other processes, including sharing data Reasons for cooperating processes: Information sharing Computation speedup Modularity Convenience Cooperating processes need interprocess communication (IPC) Two models of IPC Shared memory Message passing

13 3.13 ©2009 Operačné systémy Communications Models

14 3.14 ©2009 Operačné systémy Cooperating Processes Independent process cannot affect or be affected by the execution of another process Cooperating process can affect or be affected by the execution of another process Advantages of process cooperation Information sharing Computation speed-up Modularity Convenience

15 3.15 ©2009 Operačné systémy Producer-Consumer Problem Paradigm for cooperating processes, producer process produces information that is consumed by a consumer process unbounded-buffer places no practical limit on the size of the buffer bounded-buffer assumes that there is a fixed buffer size

16 3.16 ©2009 Operačné systémy Bounded-Buffer – Shared-Memory Solution Shared data #define BUFFER_SIZE 10 typedef struct {... } item; item buffer[BUFFER_SIZE]; int in = 0; int out = 0; Solution is correct, but can only use BUFFER_SIZE-1 elements

17 3.17 ©2009 Operačné systémy Bounded-Buffer – Producer while (true) { /* Produce an item */ while (((in = (in + 1) % BUFFER SIZE count) == out) ; /* do nothing -- no free buffers */ buffer[in] = item; in = (in + 1) % BUFFER SIZE; }

18 3.18 ©2009 Operačné systémy Bounded Buffer – Consumer while (true) { while (in == out) ; // do nothing -- nothing to consume // remove an item from the buffer item = buffer[out]; out = (out + 1) % BUFFER SIZE; return item; }

19 3.19 ©2009 Operačné systémy Interprocess Communication – Message Passing Mechanism for processes to communicate and to synchronize their actions Message system – processes communicate with each other without resorting to shared variables IPC facility provides two operations: send(message) – message size fixed or variable receive(message) If P and Q wish to communicate, they need to: establish a communication link between them exchange messages via send/receive Implementation of communication link physical (e.g., shared memory, hardware bus) logical (e.g., logical properties)

20 3.20 ©2009 Operačné systémy 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?

21 3.21 ©2009 Operačné systémy 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 A 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

22 3.22 ©2009 Operačné systémy Indirect Communication Messages are directed and received from mailboxes (also referred to as ports) Each mailbox has a unique id Processes can communicate only if they share a mailbox Properties of communication link Link established only if processes share a common mailbox A link may be associated with many processes Each pair of processes may share several communication links Link may be unidirectional or bi-directional

23 3.23 ©2009 Operačné systémy Indirect Communication Operations create a new mailbox send and receive messages through mailbox destroy a mailbox Primitives are defined as: send(A, message) – send a message to mailbox A receive(A, message) – receive a message from mailbox A

24 3.24 ©2009 Operačné systémy Indirect Communication Mailbox sharing P 1, P 2, and P 3 share mailbox A P 1, sends; P 2 and P 3 receive Who gets the message? Solutions Allow a link to be associated with at most two processes Allow only one process at a time to execute a receive operation Allow the system to select arbitrarily the receiver. Sender is notified who the receiver was.

25 3.25 ©2009 Operačné systémy Synchronization Message passing may be either blocking or non-blocking Blocking is 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-blocking is considered asynchronous Non-blocking send has the sender send the message and continue Non-blocking receive has the receiver receive a valid message or null

26 3.26 ©2009 Operačné systémy Buffering Queue of messages attached to the link; implemented in one of three ways 1.Zero capacity – 0 messages Sender must wait for receiver (rendezvous) 2.Bounded capacity – finite length of n messages Sender must wait if link full 3.Unbounded capacity – infinite length Sender never waits

27 3.27 ©2009 Operačné systémy Examples of IPC Systems - POSIX POSIX Shared Memory Process first creates shared memory segment segment id = shmget(IPC PRIVATE, size, S IRUSR | S IWUSR); Process wanting access to that shared memory must attach to it shared memory = (char *) shmat(id, NULL, 0); Now the process could write to the shared memory sprintf(shared memory, "Writing to shared memory"); When done a process can detach the shared memory from its address space shmdt(shared memory);

28 3.28 ©2009 Operačné systémy Local Procedure Calls in Windows XP

29 3.29 ©2009 Operačné systémy Communications in Client-Server Systems Sockets Remote Procedure Calls Pipes Remote Method Invocation (Java)

30 3.30 ©2009 Operačné systémy Sockets A socket is defined as an endpoint for communication Concatenation of IP address and port The socket 161.25.19.8:1625 refers to port 1625 on host 161.25.19.8 Communication consists between a pair of sockets

31 3.31 ©2009 Operačné systémy Socket Communication

32 3.32 ©2009 Operačné systémy Remote Procedure Calls Remote procedure call (RPC) abstracts procedure calls between processes on networked systems Stubs – client-side proxy for the actual procedure on the server The client-side stub locates the server and marshalls the parameters The server-side stub receives this message, unpacks the marshalled parameters, and peforms the procedure on the server

33 3.33 ©2009 Operačné systémy Execution of RPC