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…

Uses your system voice; voice and rate in settings.

≈ 9 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

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.

  • 4 See also
  • 5 References
  • 6 External links
  • Disadvantages

    edit edit source

    Merging 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 source

    Different 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 source

    Remote procedure call interfaces

    edit edit source

    Platform communication stack

    edit edit source

    The following are messaging, and information systems that utilize IPC mechanisms but don't implement IPC themselves:

    Operating system communication stack

    edit edit source

    The following are platform or programming language-specific APIs:

    Distributed object models

    edit edit source

    The following are platform or programming language specific-APIs that use IPC, but do not themselves implement it:

    See also

    edit edit source

    References

    edit edit source
    1. ^ a b "Interprocess Communications". Wikipedia revision 1376214994, retrieved 2026-11-21
    2. ^ "Inter-process communications for system-level design". International Workshop on Hardware/Software Codesign. Wikipedia revision 1376214994, retrieved 2026-11-21
    3. ^ Operating System Concepts. ISBN 978-0470128725. Wikipedia revision 1376214994, retrieved 2026-11-21
    4. ^ 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
    5. ^ Parallel Programming: Techniques and Applications Using Networked Workstations and Parallel Computers. Pearson. ISBN 978-0131405639. Wikipedia revision 1376214994, retrieved 2026-11-21
    6. ^ "Windows/WSL Interop with AF_UNIX". Microsoft. 7 February 2018. Retrieved 25 May 2018. Wikipedia revision 1376214994, retrieved 2026-11-21
    7. ^ Understanding Intel User Interrupts — HAL Science Wikipedia revision 1376214994, retrieved 2026-11-21
    8. ^ — 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
    9. ^ Extended User Interrupts (xUI): Fast and Flexible Notification without Polling — ASPLOS '25 Wikipedia revision 1376214994, retrieved 2026-11-21
    10. ^ Extended User Interrupts (xUI): Fast and Flexible Notification without Polling — Dangling Pointers Wikipedia revision 1376214994, retrieved 2026-11-21
    11. ^ "Concurrent programming - communication between processes" Wikipedia revision 1376214994, retrieved 2026-11-21
    12. ^ "IpcMain | Electron". Wikipedia revision 1376214994, retrieved 2026-11-21
    edit edit source Inter-process communicationData exchange among threads in computer programsMethods Protocols
    and standards Software libraries
    and frameworks Web syndication
    History
    Blogging
    Podcasting
    Vlogging
    Web syndication technology
    Types Technology Form Media

    Text derived from https://en.wikipedia.org/w/index.php?oldid=1376214994 under CC BY-SA 4.0; modifications have been made.

    Words in each sectionApproachesApproachesApproaches: 555 words555ApplicationsApplicationsApplications: 306 words306DisadvantagesDisadvantagesDisadvantages: 50 words50See alsoSee alsoSee also: 23 words23
    Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

    Provenance

    snapshot enwiki-001376214994 · captured 2026-09-22 · ledger · version history

    Cite this page as: encyclopegia.org, “Inter-process communication”, snapshot enwiki-001376214994. https://encyclopegia.org/a/inter-process-communication