Interprocess communication (IPC) allows processes to communicate and coordinate by sharing data. Common IPC methods include shared memory, message passing via message queues, sockets for communication over networks, and pipes for communication between related processes on the same system. These methods provide facilities for synchronization between processes and the exchange of data.
Interprocess communication (IPC) allows processes to communicate and coordinate by sharing data. Common IPC methods include shared memory, message passing via message queues, sockets for communication over networks, and pipes for communication between related processes on the same system. These methods provide facilities for synchronization between processes and the exchange of data.
Interprocess communication (IPC) allows processes to communicate and coordinate by sharing data. Common IPC methods include shared memory, message passing via message queues, sockets for communication over networks, and pipes for communication between related processes on the same system. These methods provide facilities for synchronization between processes and the exchange of data.
Interprocess communication (IPC) allows processes to communicate and coordinate by sharing data. Common IPC methods include shared memory, message passing via message queues, sockets for communication over networks, and pipes for communication between related processes on the same system. These methods provide facilities for synchronization between processes and the exchange of data.
Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1/ 32
1.
Inter process communication
Inter process communication 2. Protection and Security 3. Device management 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 Interprocess Communication Inter-process communication (IPC) is a set of methods for the exchange of data among multiple threads in one or more processes.
Processes may be running on one or more computers
connected by a network.
Operating systems provide facilities/resources for inter-
process communications (IPC), such as message queues, semaphores, and shared memory. Interprocess Communication Methods Inter-process communication techniques can be divided into various types. These are:
1. Shared memory 2. Message Passing / Message Queue 3. Sockets 4. Pipes 5. FIFO (Named Pipes) Interprocess Communication Methods Shared memory: Shared memory is an efficient means of passing data between programs. An area is created in memory by a process, which is accessible by another process. Processes communicate by reading and writing to that memory space.
Message queues: By using this method, a developer can
pass messages between processes via a single queue or a number of message queues. A system kernel manages this mechanism. Interprocess Communication Methods
Shared Memory Also known as 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:
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 Message Passing Also known as In-direct 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 Link may be unidirectional or bi-directional IPC: Message Passing Operations create a new mailbox send and receive messages through mailbox destroy a mailbox
Operations/ Primitives are defined as:
send(mailbox, message) – send message to mail box receive(mailbox, message) – mailbox receives message. send(A, message) – send a message to mailbox A receive(A, message) – receive a message from mailbox A IPC: Message Passing Synchronization • Message passing may be either: - Blocking - Non-blocking
1. 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 IPC: Message Passing Synchronization 2. 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 Message Queues The messages that pass through the queue have two components: one that describes the message (header) an one holding the content (message body).
There is no designated structure for the message body, so the users
can define their own message types having different structure and dimension.
The access to the queue is automatically synchronized by the
operating system, such that if several processes wish to perform read and write operations upon the queue, its content remains consistent. Interprocess Communication Methods Sockets: We use this mechanism to communicate over a network, between a client and a server. This method facilitates a standard connection that is independent of the type of computer and the type of operating system used.
FIFO: A FIFO or 'first in, first out' is a one-way flow of data.
FIFOs are similar to pipes FIFOs are identified in the file system with a name. FIFOs are 'named pipes'. Communication in Client-Server Systems
Basic methods user are:
1. Sockets 2. Pipe Sockets A network socket is an endpoint of an inter-process communication flow across a computer network.
A socket address is the combination of an IP address
and a port number, much like one end of a telephone connection is the combination of a phone number and a particular extension. Communication in Client-Server Systems Sockets Defined as end point of communication Pair of processes communicate over the network user sockets- one socket for each process Socket is identified by an IP address which is concatenated with port number Server listen to client via a port, server receives the request and complete the connection. Communication in Client-Server Systems Sockets are created using socket() system call. It takes: Communication Domain Socket type Protocol to be used: as argument Sockets Based on this address, internet sockets deliver incoming data packets to the appropriate application process or thread.
A socket API is an application programming interface
(API), usually provided by the operating system, that allows application programs to control and use network sockets. Internet socket APIs are usually based on the Berkeley sockets standard. Sockets There are several Internet socket types available:
Datagram sockets, also known as connectionless sockets,
E.g. User Datagram Protocol(UDP) (used for Broadcasting)
Stream sockets, also known as connection-oriented sockets
E.g: Transmission Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP). (used for Peer to Peer)
Raw sockets (or Raw IP sockets), typically available in
routers and other network equipment. Pipe A pipe is a communication channel between two ends. It is mostly used to communicate between processes running within a computer.
It is used on the command line to direct the output of a
command as input of the next command.
A pipe is created by a process, that process calls fork,
and the pipe is used between the parent and the child. Pipe linking shell commands together so that the output of one process is fed straight to the input of another. For shell commands, this is done using the pipe character to join the commands, such as cmd1 | cmd2. Pipe Pipes have two limitations.
They have been half duplex (i.e., data flows in only one direction).
Pipes can be used only between processes that have a
common ancestor (parent). Pipe Pipe() is a system call that facilitates inter-process communication.
Pipe opens a virtual file, which is used for
communication between parent and child.
One process can write to this "virtual file" or pipe and
another related process can read from it. Types of Pipe Unnamed Virtual file used to send data between 2 processes. Unnamed pipe can only work with related process.
Named or FIFO Created by using mkfifo command It is a permanent file. FIFO is same to unnamed file but with a facility that it can be accessed from anywhere. Interprocess Communication If a process tries to read before something is written to the pipe, the process is suspended until something is written.
Syntax : Interprocess Communication Two file descriptors are returned through the fileds argument: fd[0] is open for reading, and fd[1] is open for writing. The output of filedes[1] is the input for filedes[0]. Popen and pclose The simplest way of passing data between two programs is with the popen and pclose functions.
The popen function allows a program to invoke another program
as a new process and either pass data to it or receive data from it.
The command string is the name of the program to run, together with any parameters. open_mode must be either “r” or “w”. Popen and pclose Flow of data is in both directions
A call to popen must specify either “r” or “w”;
When the process started with popen has finished, you can close the file stream associated with it using pclose.
The pclose call will return only when the process started with popen finishes.
If it’s still running when pclose is called, the pclose call will wait for the process to finish. Popen and pclose If type is "r", the file pointer is connected to the standard output of cmd string. (i.e read into)
If type is "w", the file pointer is connected to the standard
input of cmd string (i.e write into) Popen and pclose popen :
Arguments : 1. command that will be executed by the child process. 2. The type of communication by the parent, i.e. whether the parent is going to read from the pipe or write into the pipe. Return : It returns a file descriptor that gets created as a result of call to the pipe.
