Inter-process communication (pipes, shared memory) in Operating Systems - Step-by-Step Execution

Concept Flow - Inter-process communication (pipes, shared memory)

Process A wants to send data

↓

Choose IPC method

↓

Pipes

↓

Write data

↓

Data flows

↓

Process B reads data

↓

Communication complete

This flow shows how two processes communicate by choosing either pipes or shared memory, then sending and receiving data.

Execution Sample

Operating Systems

Process A creates pipe
Process A writes 'Hello'
Process B reads from pipe
Process B prints message

Process A sends a message 'Hello' to Process B using a pipe.

Analysis Table

Step	Action	Data State	Process A State	Process B State
1	Create pipe	Pipe created, empty	Ready to write	Ready to read
2	Process A writes 'Hello'	Pipe contains 'Hello'	Data sent	Waiting to read
3	Process B reads from pipe	Pipe empty after read	Data sent	Received 'Hello'
4	Process B prints message	Pipe empty	Data sent	Printed 'Hello'
5	Communication ends	Pipe closed	Done	Done

💡 Pipe closed after data transfer, communication ends

State Tracker

Variable	Start	After Step 2	After Step 3	Final
Pipe Buffer	empty	'Hello'	empty	closed
Process A State	Ready to write	Data sent	Data sent	Done
Process B State	Ready to read	Waiting to read	Received 'Hello'	Done

Key Insights - 2 Insights

Why does Process B see the pipe as empty after reading?

Because reading from a pipe removes the data, as shown in step 3 of the execution_table where the pipe buffer changes from 'Hello' to empty.

How is shared memory different from pipes in data access?

Shared memory allows both processes to access the same memory area directly, unlike pipes which transfer data in one direction and remove it after reading.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what is the state of the pipe buffer?

A 'Hello'

B empty

C closed

D unknown

💡 Hint

Check the 'Data State' column at step 2 in the execution_table.

At which step does Process B receive the message?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Process B State' column in the execution_table.

If Process A writes data twice before Process B reads, how would the pipe buffer change?

A It would be empty immediately

B It would only contain the last message

C It would contain both messages concatenated

D It would cause an error

💡 Hint

Pipes buffer data in order until read, so multiple writes accumulate.

Concept Snapshot

Inter-process communication (IPC) allows processes to exchange data.
Pipes provide a one-way data channel; data is removed once read.
Shared memory lets processes access the same memory area directly.
Pipes are simple but limited; shared memory is faster but needs synchronization.
Choose IPC method based on communication needs.

Full Transcript

Inter-process communication (IPC) is how two processes share data. Pipes create a channel where one process writes data and the other reads it. When data is read from a pipe, it is removed, so the pipe becomes empty. Shared memory allows both processes to access the same memory space directly, which is faster but requires careful coordination. The execution table shows step-by-step how Process A writes 'Hello' to a pipe, Process B reads it, and then prints it. Variables like the pipe buffer and process states change accordingly. Understanding these steps helps clarify how data flows between processes.

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