Programmed I/O vs interrupt-driven I/O in Operating Systems - Visual Side-by-Side Comparison

Concept Flow - Programmed I/O vs interrupt-driven I/O

Start I/O Operation

↓

Programmed I/O?

Yes→CPU waits and checks device status repeatedly

↓

Data transfer when ready

↓

Interrupt-driven I/O?

Yes→CPU does other work

↓

Device sends interrupt when ready

↓

Invalid method

↓

End

↓

End

The flow shows two ways CPU handles I/O: Programmed I/O where CPU waits actively, and Interrupt-driven I/O where CPU works and responds when device signals.

Execution Sample

Operating Systems

while (device_not_ready) {
  // wait and check device status
}
read_data_from_device();

This code shows Programmed I/O where CPU waits in a loop checking device readiness before reading data.

Analysis Table

Step	CPU Action	Device Status Check	CPU State	Data Transfer
1	Check device status	Not ready	Waiting	No
2	Check device status	Not ready	Waiting	No
3	Check device status	Ready	Proceed	No
4	Read data	Ready	Reading	Yes
5	End	-	-	-

💡 Device becomes ready at step 3, CPU stops waiting and reads data.

State Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
device_status	Not ready	Not ready	Not ready	Ready	Ready	Ready
CPU_state	Idle	Waiting	Waiting	Proceed	Reading	Idle

Key Insights - 2 Insights

Why does the CPU waste time in Programmed I/O?

Because it keeps checking device status repeatedly (see execution_table steps 1 and 2), it cannot do other work until device is ready.

How does Interrupt-driven I/O improve CPU efficiency?

CPU does other tasks and only stops when device sends an interrupt signal, avoiding constant checking (not shown in programmed I/O table but explained in concept_flow).

Visual Quiz - 3 Questions

In the execution_table, what is the CPU state at step 2?

A Reading

B Waiting

C Idle

D Proceed

💡 Hint

Look at the 'CPU State' column in execution_table row for step 2.

At which step does the device become ready according to the execution_table?

A Step 3

B Step 4

C Step 1

D Step 5

💡 Hint

Check the 'Device Status Check' column to find when status changes to 'Ready'.

If the device never becomes ready, what happens to the CPU in Programmed I/O?

A CPU switches to other tasks automatically

B CPU shuts down

C CPU continues waiting indefinitely

D CPU reads data anyway

💡 Hint

Refer to execution_table steps 1 and 2 where CPU waits while device is not ready.

Concept Snapshot

Programmed I/O: CPU waits and checks device status in a loop, blocking other tasks.
Interrupt-driven I/O: CPU does other work and responds only when device sends an interrupt.
Programmed I/O wastes CPU time; interrupt-driven I/O improves efficiency.
Interrupts signal CPU to handle I/O asynchronously.
Use programmed I/O for simple devices; interrupts for multitasking systems.

Full Transcript

This visual execution compares Programmed I/O and Interrupt-driven I/O. Programmed I/O makes the CPU wait actively by checking device status repeatedly until the device is ready, shown in the execution table steps 1 to 3. The CPU state remains waiting until the device signals readiness, then it reads data. Interrupt-driven I/O lets the CPU do other work and only stop when the device sends an interrupt signal, improving efficiency. The variable tracker shows device status and CPU state changes over time. Key moments clarify why programmed I/O wastes CPU time and how interrupts help. The quiz tests understanding of CPU states and device readiness during execution.