1. InterProcess Communication

2. 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 – Data Transfer

3. 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

4. Communications Models Message Passing Shared Memory

5. Producer-Consumer Problem Paradigm for cooperating processes, producer process produces information that is consumed by a consumer process

6. IPC Data Transfer – 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)

7. 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?

8. 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

9. 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

10. 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

11. 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.

12. 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

13. 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

14. Examples of IPC System PIPES nData streaming nDirect communication nOrdinary pipes Producer – Consumer fashion Cannot be accessed outside the process that creates it. Usually Parent – Child communication Deleted when process terminates nNamed pipes lAlias: FIFO in unix lAppear as typical files in the system

15. POSIX POSIX, an acronym for "Portable Operating System Interface", is a family of standards specified by the IEEE for maintaining compatibility between operating systems. POSIX defines the application programming interface (API), along with command line shells and utility interfaces, for software compatibility with variants of Unix and other operating systems. http://en.wikipedia.org/wiki/POSIX

16. Examples of IPC Systems - POSIX POSIX Message Passing Processes can exchange messages by using four system calls: nmsgget(mailbox_name, IPC_CREAT) Converts a mailbox name to a message queue ID (msqid). It will create the mailbox if necessary. Returns the msqid. nmsgsnd(msqid, message@, message_size) Sends the message to the mailbox nmsgrcv( msqid, message@, message_size, priority, synch/asynch) Receives the message from the mailbox nmsgctl(msqid, IPC_RMID, dummyParam@) Release the mailbox from process resources

17. Communications in Client-Server Systems Sockets Remote Procedure Calls

18. 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

19. Socket Communication

20. Socket

21. 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

22. Execution of RPC

23. Examples of IPC Systems - Mach Mach communication is message based – Even system calls are messages – Each task gets two mailboxes at creation- Kernel and Notify – Only three system calls needed for message transfer msg_send(), msg_receive(), msg_rpc() – Mailboxes needed for commuication, created via port_allocate()

24. Examples of IPC Systems – Windows XP Message-passing centric via local procedure call (LPC) facility – Only works between processes on the same system – Uses ports (like mailboxes) to establish and maintain communication channels – Communication works as follows: The client opens a handle to the subsystem’s connection port object The client sends a connection request The server creates two private communication ports and returns the handle to one of them to the client The client and server use the corresponding port handle to send messages or callbacks and to listen for replies

25. Examples of IPC Systems Shared Memory 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);

26. Shell Assignment A shell is a job control system – Allows programmer to create and manage a set of programs to do some task – Windows, MacOS, Linux all have shells Example: to compile a C program cc –c sourcefile1.c cc –c sourcefile2.c ln –o program sourcefile1.o sourcefile2.o

27. System Call : fork() Create a child process Returns to both the child and parent

28. System Call : exec() Run application in current process exec(prog, args) Execl( pathname, arg[0], arg[1]…. 0) Excelp(arg[0], arg[1]…. 0) http://www.yolinux.com/TUTORIALS/ForkExecPr ocesses.html

29. System Call: wait() Pause until child process has exited wait(): Blocks calling process until the child process terminates. If child process has already teminated, the wait() call returns immediately. if the calling process has multiple child processes, the function returns when one returns. waitpid(): Options available to block calling process for a particular child process not the first one http://www.yolinux.com/TUTORIALS/ForkExecProcesse s.html http://www.yolinux.com/TUTORIALS/ForkExecProcesse s.html

30. System call : system() Invokes the command processor to execute a command. Uses fork() exec() and wait() The call "blocks" and waits for the task to be performed before continuing. system(“ls –l”);

31. UNIX Signal Facility for one process to send another instant notification Send an interrupt to a process signal(processID, type) Signal Handling example – http://www.yolinux.com/TUTORIALS/C++Signals.h tml http://www.yolinux.com/TUTORIALS/C++Signals.h tml

32. System Call : dup2() Replace the tofileDesc file descriptor with a copy of the fromfiledesc file descriptor. Used for replacing stdin or stdout or both in a child process dup2(fromFileDesc, toFileDesc) Example: http://www.cs.loyola.edu/~jglenn/702/S2005/Exam ples/pipe.html

33. Implementing a Shell char *prog, **args; int child_pid; // Read and parse the input a line at a time while (readAndParseCmdLine(&prog, &args)) { child_pid = fork(); // create a child process if (child_pid == 0) { exec(prog, args); // I'm the child process. Run program // NOT REACHED } else { wait(child_pid); // I'm the parent, wait for child return 0; }