Inter-process communication
system that connects many personal computers over the Internet via inter-process network communication In computer science, inter-process communication (IPC) is the sharing of data between running processes in a computer system, or between…
≈ 9 min read
Inter-process communication. encyclopegia.org, snapshot enwiki-001376214994. /a/inter-process-communication
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
In computer science, inter-process communication (IPC) is the sharing of data between running processes in a computer system, or between multiple such systems. Mechanisms for IPC may be provided by an operating system. Applications which use IPC are often categorized as using clients and servers, where the client process requests data and the server process responds to client requests.[1].
IPC is very important to the design process for microkernels and nanokernels, which reduce the number of functionalities provided by the kernel. Those functionalities are then obtained by messaging with IPC servers (specialized coordination application), leading to a large increase in communication when compared to a regular monolithic kernel (central, with less spawn independent processes). IPC interfaces generally encompass variable analytic framework structures. This IPCs methods ensure compatibility between the multi-vector protocols upon which IPC models rely.[2]
An IPC mechanism is either synchronous or asynchronous. Synchronization primitives may be used to have synchronous behavior with an asynchronous IPC mechanism.
Disadvantages
edit edit sourceMerging data from two processes can often incur significantly higher costs compared to processing the same data on a single thread, potentially by two or more orders of magnitude due to overheads such as inter-process communication and synchronization.[3][4][5]
Approaches
edit edit sourceDifferent IPC approaches are tailored to different process requirements (inside an application), such as performance, modularity, and system circumstances such as network bandwidth (an optimal consideration, but depends on the application distribution) and latency (general cost and density of generating and processing requests).[1]
| Method | Short Description | Provided by (operating systems or other environments) |
|---|---|---|
| File | A record stored on disk, or a record synthesized on demand by a file server, which can be accessed by multiple processes. | Most operating systems |
| Communications file | A unique form of IPC in the late-1960s that most closely resembles Plan 9's 9P protocol | Dartmouth Time-Sharing System |
| Signal; also Asynchronous System Trap | A system message sent from one process to another, not usually used to transfer data but instead used to remotely command the partnered process. | Most operating systems |
| Socket | Data sent over a network interface, either to a different process on the same computer or to another computer on the network. Stream-oriented (TCP; data written through a socket requires formatting to preserve message boundaries) or more rarely message-oriented (UDP, SCTP). | Most operating systems |
| Unix domain socket | Similar to an internet socket, but all communication occurs within the kernel. Domain sockets use the file system as their address space. Processes reference a domain socket as an inode, and multiple processes can communicate with one socket | All POSIX operating systems and Windows 10[6] |
| Message queue | A data stream similar to a socket, but which usually preserves message boundaries. Typically implemented by the operating system, they allow multiple processes to read and write to the message queue without being directly connected to each other. | Most operating systems |
| Anonymous pipe | A unidirectional data channel using standard input and output. Data written to the write-end of the pipe is buffered by the operating system until it is read from the read-end of the pipe. Two-way communication between processes can be achieved by using two pipes in opposite "directions". | All POSIX systems, Windows |
| Named pipe | A pipe that is treated like a file. Instead of using standard input and output as with an anonymous pipe, processes write to and read from a named pipe, as if it were a regular file. | All POSIX systems, Windows, AmigaOS 2.0+ |
| Shared memory | Multiple processes are given access to the same block of memory, which creates a shared buffer for the processes to communicate with each other. | All POSIX systems, Windows |
| Message passing | Allows multiple programs to communicate using message queues and/or non-OS managed channels. Commonly used in concurrency models. | Used in LPC, RPC, RMI, and MPI paradigms, Java RMI, CORBA, COM, DDS, MSMQ, MailSlots, QNX, GNU Hurd, others |
| Memory-mapped file | A file mapped to RAM and can be modified by changing memory addresses directly instead of outputting to a stream. This shares the same benefits as a standard file. | All POSIX systems, Windows |
| User interrupts (UIPI)[7] | Equivalent to syscalls, but for user mode IPC. ≥9× performance improvement over other IPC mechanisms for event signaling[8], due to hardware support. | Only on CPUs with the UINTR instruction set, like Sapphire Rapids. |
| Extended User Interrupts (xUI)[9] | Improvement on UIPI, solving the performance problem of UPII-caused pipeline flushes with tracked interrupts.[10] | As of 2026, purely theoretical, with no know implementations. |
Applications
edit edit sourceRemote procedure call interfaces
edit edit source- Java's Remote Method Invocation (RMI)
- ONC RPC
- XML-RPC or SOAP
- JSON-RPC
- Message Bus (Mbus) (specified in RFC 3259) (not to be confused with M-Bus)
- .NET Remoting
- gRPC
Platform communication stack
edit edit sourceThe following are messaging, and information systems that utilize IPC mechanisms but don't implement IPC themselves:
- KDE's Desktop Communications Protocol (DCOP) – deprecated by D-Bus
- D-Bus
- OpenWrt uses ubus micro bus architecture
- MCAPI Multicore Communications API
- SIMPL The Synchronous Interprocess Messaging Project for Linux (SIMPL)
- 9P (Plan 9 Filesystem Protocol)
- Distributed Computing Environment (DCE)
- Thrift
- ZeroC's Internet Communications Engine (ICE)
- ØMQ
- YAMI4
- Enlightenment_(software) E16 uses eesh as an IPC
Operating system communication stack
edit edit sourceThe following are platform or programming language-specific APIs:
- Apple Computer's Apple events, previously known as Interapplication Communications (IAC)
- ARexx ports
- Enea's LINX for Linux (open source) and various DSP and general-purpose processors under OSE
- The Mach kernel's Mach Ports
- Microsoft's ActiveX, Component Object Model (COM), Microsoft Transaction Server (COM+), Distributed Component Object Model (DCOM), Dynamic Data Exchange (DDE), Object Linking and Embedding (OLE), anonymous pipes, named pipes, Local Procedure Call, MailSlots, Message loop, MSRPC, .NET Remoting, and Windows Communication Foundation (WCF)
- Novell's SPX
- POSIX mmap, message queues, semaphores,[11] and shared memory
- RISC OS's messages
- Solaris Doors
- System V's message queues, semaphores, and shared memory
- Linux Transparent Inter Process Communication (TIPC)
- OpenBinder Open binder
- QNX's PPS (Persistent Publish/Subscribe) service
Distributed object models
edit edit sourceThe following are platform or programming language specific-APIs that use IPC, but do not themselves implement it:
- PHP's sessions
- Distributed Ruby
- Common Object Request Broker Architecture (CORBA)
- Electron's asynchronous IPC, shares JSON objects between a main and a renderer process[12]
See also
edit edit source- Berkeley sockets
- Computer network programming
- Communicating Sequential Processes (CSP paradigm)
- Data Distribution Service
- Database-as-IPC
- Protected procedure call
References
edit edit source- Stevens, Richard (1999). UNIX Network Programming. Interprocess Communications. Vol. 2 (Second ed.). Prentice Hall. ISBN 0-13-081081-9.
- Ramachandran, U.; Solomon, M.; Vernon, M. (1987). "Hardware support for interprocess communication". Proceedings of the 14th annual international symposium on Computer architecture. Pittsburgh, Pennsylvania, United States. pp. 178–188. ISBN 0-8186-0776-9.
{{cite book}}: CS1 maint: location missing publisher (link) - Crovella, M.; Bianchini, R.; LeBlanc, T.; Markatos, E.; Wisniewski, R. (1–4 December 1992). Using communication-to-computation ratio in parallel program designand performance prediction. pp. 238–245. ISBN 0-8186-3200-3.
- ^ a b "Interprocess Communications". Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ "Inter-process communications for system-level design". International Workshop on Hardware/Software Codesign. Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Operating System Concepts. ISBN 978-0470128725. Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Computer Organization and Design MIPS Edition: The Hardware/Software Interface (The Morgan Kaufmann Series in Computer Architecture and Design). Morgan Kaufmann. ISBN 978-0124077263. Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Parallel Programming: Techniques and Applications Using Networked Workstations and Parallel Computers. Pearson. ISBN 978-0131405639. Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ "Windows/WSL Interop with AF_UNIX". Microsoft. 7 February 2018. Retrieved 25 May 2018. Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Understanding Intel User Interrupts — HAL Science Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ — x86 User Interrupts support — x86-AT-kernel.org mailing list (See section “Why care about this? - Micro benchmark performance”.) Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Extended User Interrupts (xUI): Fast and Flexible Notification without Polling — ASPLOS '25 Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ Extended User Interrupts (xUI): Fast and Flexible Notification without Polling — Dangling Pointers Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ "Concurrent programming - communication between processes" Wikipedia revision 1376214994, retrieved 2026-11-21
- ^ "IpcMain | Electron". Wikipedia revision 1376214994, retrieved 2026-11-21
External links
edit edit source- Linux ipc(5) man page describing System V IPC
- Windows IPC
- IPC available using Qt
- Unix Network Programming (Vol 2: Interprocess Communications) by W. Richard Stevens
- Interprocess Communication and Pipes in C
- DIPC, Distributed System V IPC
and standards
and frameworks
Text derived from https://en.wikipedia.org/w/index.php?oldid=1376214994 under CC BY-SA 4.0; modifications have been made.