Skip to content

Latest commit

 

History

History
44 lines (31 loc) · 3.22 KB

IPC.md

File metadata and controls

44 lines (31 loc) · 3.22 KB
Raw

Interprocess Communications

Methods in Interprocess Communication

Inter-process communication (IPC) is set of interfaces, which is usually programmed in order for the programs to communicate between series of processes. This allows running programs concurrently in an Operating System. These are the methods in IPC:

  • Pipes (Same Process)

    • This allows flow of data in one direction only. Analogous to simplex systems (Keyboard). Data from the output is usually buffered until input process receives it which must have a common origin.
    • Explanation & Example

  • Named Pipes (Different Processes)

    • This is a pipe with a specific name it can be used in processes that don’t have a shared common process origin. E.g. is FIFO where the details written to a pipe is first named.
    • Explanation & Example

  • Message Queuing

    • This allows messages to be passed between processes using either a single queue or several message queue. This is managed by system kernel these messages are coordinated using an API.
    • Explanation & Example

  • Semaphores

    • This is used in solving problems associated with synchronization and to avoid race condition. These are integer values which are greater than or equal to 0.
    • Explanation & Exmaple

  • Shared memory

    • This allows the interchange of data through a defined area of memory. Semaphore values have to be obtained before data can get access to shared memory.
    • Explanation & Exmaple

  • Sockets

    • This method is mostly used to communicate over a network between a client and a server. It allows for a standard connection which is computer and OS independent.

  • Signals

  • Memory Mapping

Detailed Explanations

Implementation

Brendan's Multi-tasking Tutorial

This tutorial will describe a way to implement multi-tasking and task switching for a kernel that uses "kernel stack per task". It has been designed to allow the reader to implement a full featured scheduler (while avoiding common pitfalls) in steps that can be tested before moving on to the next step.