Inter-process communication (pipes, shared memory) in Operating Systems - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Inter-process Communication (IPC)?

IPC is a way for different processes running on the same or different computers to exchange data and signals to coordinate their actions.

beginner

How do pipes facilitate communication between processes?

Pipes allow one process to send data to another in a unidirectional flow, like a pipe carrying water from one place to another.

beginner

What is shared memory in IPC?

Shared memory is a method where multiple processes access the same memory space to read and write data quickly without copying it between processes.

intermediate

What is the main difference between pipes and shared memory?

Pipes send data in a stream from one process to another, while shared memory allows multiple processes to access the same memory area directly.

intermediate

Why is synchronization important in shared memory IPC?

Because multiple processes can access the same memory at the same time, synchronization prevents conflicts and ensures data is consistent and not corrupted.

Which IPC method allows data to flow in one direction between processes?

A Message queue

B Pipe

C Shared memory

D Semaphore

Pipes provide a unidirectional data flow from one process to another.

What is a key advantage of shared memory over pipes?

A Only works between parent and child processes

B Data is copied multiple times

C Faster data exchange by direct memory access

D Data flows only one way

Shared memory allows processes to access the same memory area directly, making data exchange faster.

Why do processes using shared memory need synchronization?

A To prevent data corruption from simultaneous access

B To increase data copying speed

C To allow unidirectional data flow

D To create separate memory spaces

Synchronization prevents conflicts when multiple processes access shared memory at the same time.

Which IPC method is typically simpler to use but slower for large data?

A Shared memory

B Signals

C Sockets

D Pipes

Pipes are simpler but involve copying data, which can be slower for large amounts.

In which scenario is shared memory most useful?

A When processes need to share large amounts of data efficiently

B When processes need to send small messages quickly

C When processes run on different machines

D When only one process is running

Shared memory is ideal for efficient sharing of large data between processes.

Explain how pipes work for inter-process communication and give a real-life example.

Think about how water flows through a pipe from one place to another.

Describe shared memory IPC and why synchronization is necessary.

Imagine several people writing on the same whiteboard at once.

Practice

1. Which of the following best describes a pipe in inter-process communication?

easy

A. A way to create new processes in the operating system

B. A memory area shared by multiple processes simultaneously

C. A method to encrypt data between processes

D. A channel that sends data in a stream from one process to another

Solution

1. Step 1: Understand what a pipe does

   A pipe is used to send data in a continuous stream from one process to another, allowing communication.

2. Step 2: Compare with other options

   Shared memory allows direct access to the same data, encryption is unrelated, and process creation is a different concept.

3. Final Answer:

   A channel that sends data in a stream from one process to another -> Option D

4. Quick Check:

   Pipe = Stream data channel [OK]

Hint: Pipes stream data between processes, shared memory shares data directly [OK]

Common Mistakes:

• Confusing pipes with shared memory
• Thinking pipes create processes
• Assuming pipes encrypt data

2. Which of the following is the correct syntax to create a pipe in a Unix-like operating system using C?

easy

A. pipe(int *fd);

B. pipe(fd);

C. pipe(int fd[2]);

D. pipe(fd[2]);

Solution

1. Step 1: Recall the pipe function signature

   The pipe function requires an integer array of size 2 passed by reference to store file descriptors.

2. Step 2: Match the correct syntax

   The correct syntax is pipe(fd); where fd is an integer array of size 2 declared before the call.

3. Final Answer:

   pipe(fd); -> Option B

4. Quick Check:

   pipe needs int array of size 2 [OK]

Hint: pipe() needs int array of size 2 as argument [OK]

Common Mistakes:

• Omitting the type in the argument
• Passing pointer instead of array
• Passing array without size

3. Consider the following pseudo-code using shared memory:

1. Create shared memory segment
2. Process A writes value 10 to shared memory
3. Process B reads value from shared memory
4. Process B writes value 20 to shared memory
5. Process A reads value from shared memory

What value will Process A read in step 5?

medium

A. 20

B. 10

C. 0

D. Undefined or error

Solution

1. Step 1: Track writes and reads in shared memory

   Process A writes 10, then Process B reads 10, then Process B writes 20.

2. Step 2: Determine what Process A reads after Process B's write

   Since shared memory is common, Process A will read the updated value 20.

3. Final Answer:

   20 -> Option A

4. Quick Check:

   Shared memory shows last written value [OK]

Hint: Shared memory shows latest written value to all processes [OK]

Common Mistakes:

• Assuming Process A reads its own old value
• Thinking reads cause errors
• Confusing shared memory with pipes

4. A programmer tries to use a pipe for communication but notices the reading process blocks indefinitely. What is the most likely cause?

medium

A. Shared memory was used instead of a pipe

B. The pipe was created with incorrect syntax

C. The writing process has not sent any data yet

D. The pipe buffer size is too large

Solution

1. Step 1: Understand pipe blocking behavior

   A reading process blocks if no data is available to read from the pipe.

2. Step 2: Identify the cause of blocking

   If the writing process has not sent data, the reader waits indefinitely for input.

3. Final Answer:

   The writing process has not sent any data yet -> Option C

4. Quick Check:

   Reader blocks if no data sent [OK]

Hint: Reader waits until writer sends data through pipe [OK]

Common Mistakes:

• Blaming syntax errors for blocking
• Confusing pipe with shared memory
• Assuming buffer size causes blocking

5. You want two processes to share a large data structure efficiently and allow both to read and write it. Which IPC method is best and why?

hard

A. Use shared memory because it allows direct access to the same data

B. Use sockets because they work over networks

C. Use message queues because they guarantee message order

D. Use pipes because they provide fast streaming of data

Solution

1. Step 1: Analyze requirements for sharing large data structure

   Efficient sharing with read/write access means processes need direct access to the same memory.

2. Step 2: Compare IPC methods

   Pipes stream data but are unidirectional and less efficient for large shared data. Message queues and sockets add overhead and are for message passing, not direct shared access.

3. Final Answer:

   Use shared memory because it allows direct access to the same data -> Option A

4. Quick Check:

   Shared memory = direct, efficient data sharing [OK]

Hint: Shared memory is best for large, read/write shared data [OK]

Common Mistakes:

• Choosing pipes for large data sharing
• Confusing message queues with shared memory
• Thinking sockets are best for local IPC