Programmed I/O vs interrupt-driven I/O in Operating Systems - Key Differences Explained

Introduction

Imagine you want to get data from a device like a keyboard or a disk. The problem is how the computer should wait for this data without wasting time or missing it. Two common ways to handle this are programmed input/output and interrupt-driven input/output.

Explanation

Programmed I/O

In programmed I/O, the computer's processor actively checks the device repeatedly to see if it is ready to send or receive data. This checking is called polling. The processor waits in a loop until the device is ready, which can waste time because the processor cannot do other tasks during this waiting.

Programmed I/O makes the processor wait and check the device continuously, which can waste processing time.

Interrupt-driven I/O

In interrupt-driven I/O, the device tells the processor when it is ready by sending an interrupt signal. The processor can do other work and only stops to handle the device when it receives this signal. This way, the processor is not wasting time waiting and can be more efficient.

Interrupt-driven I/O lets the device notify the processor, so the processor can work on other tasks until needed.

Processor Involvement

Programmed I/O requires the processor to be involved constantly, checking the device status. Interrupt-driven I/O reduces this involvement by allowing the processor to respond only when the device signals it, freeing the processor for other work.

Interrupt-driven I/O reduces processor involvement compared to programmed I/O.

Efficiency and Use Cases

Programmed I/O is simple but inefficient for slow devices because the processor wastes time polling. Interrupt-driven I/O is more efficient, especially when devices are slow or data comes irregularly, as it allows better multitasking and resource use.

Interrupt-driven I/O is more efficient and better for multitasking than programmed I/O.

Real World Analogy

Imagine you are waiting for a friend to arrive. In programmed I/O, you keep looking out the window every minute to see if they are there, which wastes your time. In interrupt-driven I/O, you do your work and your friend calls you when they arrive, so you only stop when needed.

Programmed I/O → Looking out the window repeatedly to check if the friend has arrived

Interrupt-driven I/O → Friend calling you to announce their arrival

Processor Involvement → Your attention being fully on watching the window versus doing other tasks

Efficiency and Use Cases → Wasting time watching the window versus using time effectively until called

Diagram

Diagram

┌─────────────────────┐          ┌─────────────────────┐
│    Programmed I/O    │          │ Interrupt-driven I/O│
├─────────────────────┤          ├─────────────────────┤
│ Processor polls      │          │ Device sends        │
│ device status in a   │          │ interrupt signal    │
│ loop, waiting        │          │ when ready          │
│                     │          │                     │
│ Processor busy       │          │ Processor does other │
│ waiting              │          │ work until interrupt│
└─────────┬───────────┘          └─────────┬───────────┘
          │                                │
          │                                │
          ▼                                ▼
   Device ready                     Device ready
   data transfer                   data transfer

This diagram compares how programmed I/O keeps the processor busy polling the device, while interrupt-driven I/O lets the processor work until the device signals readiness.

Key Facts

Programmed I/O → Processor continuously checks device status in a loop to transfer data.

Interrupt-driven I/O → Device sends an interrupt signal to processor when it is ready for data transfer.

Polling → The process of repeatedly checking the status of a device.

Interrupt → A signal from a device that alerts the processor to stop current work and handle the device.

Processor Efficiency → Interrupt-driven I/O improves efficiency by freeing the processor from constant checking.

Common Confusions

Thinking programmed I/O allows the processor to do other tasks while waiting.

Thinking programmed I/O allows the processor to do other tasks while waiting. In programmed I/O, the processor is busy polling and cannot perform other tasks effectively during this time.

Believing interrupts cause the processor to stop all work immediately.

Believing interrupts cause the processor to stop all work immediately. Interrupts pause the current task briefly to handle the device, then the processor resumes its previous work.

Summary

Programmed I/O wastes processor time by making it check the device repeatedly.

Interrupt-driven I/O lets the device notify the processor, improving efficiency and multitasking.

Choosing between these methods depends on device speed and system needs.

Practice

1. Which of the following best describes programmed I/O?

easy

A. CPU ignores the device until a scheduled time

B. Device sends a signal to CPU only when it needs attention

C. CPU and device communicate using direct memory access

D. CPU continuously checks the device status until it is ready

Solution

1. Step 1: Understand programmed I/O behavior

   Programmed I/O means the CPU actively checks the device repeatedly to see if it is ready.

2. Step 2: Compare options with definition

   CPU continuously checks the device status until it is ready matches this behavior exactly, while others describe interrupt or other methods.

3. Final Answer:

   CPU continuously checks the device status until it is ready -> Option D

4. Quick Check:

   Programmed I/O = CPU polls device [OK]

Hint: Programmed I/O means CPU keeps checking device status [OK]

Common Mistakes:

• Confusing programmed I/O with interrupt-driven I/O
• Thinking device signals CPU in programmed I/O
• Mixing up direct memory access with programmed I/O

2. Which of the following is the correct statement about interrupt-driven I/O?

easy

A. Device interrupts CPU only when it needs service

B. CPU waits in a loop checking device status

C. CPU ignores device signals completely

D. CPU uses programmed polling to check device

Solution

1. Step 1: Recall interrupt-driven I/O definition

   Interrupt-driven I/O means the device sends a signal (interrupt) to the CPU when it needs attention.

2. Step 2: Match options to definition

   Device interrupts CPU only when it needs service correctly states that the device interrupts the CPU only when service is needed.

3. Final Answer:

   Device interrupts CPU only when it needs service -> Option A

4. Quick Check:

   Interrupt-driven I/O = device signals CPU [OK]

Hint: Interrupt-driven means device signals CPU when ready [OK]

Common Mistakes:

• Choosing options describing CPU polling
• Assuming CPU ignores device signals
• Confusing programmed I/O with interrupt-driven I/O

3. Consider this scenario: A CPU uses programmed I/O to read data from a device. What is the main effect on CPU usage?

medium

A. CPU can perform other tasks while waiting for device

B. CPU is busy checking device status and cannot do other work

C. CPU ignores the device until data is ready

D. CPU receives an interrupt when device is ready

Solution

1. Step 1: Understand CPU behavior in programmed I/O

   In programmed I/O, CPU repeatedly checks device status, which keeps it busy and unable to do other tasks efficiently.

2. Step 2: Analyze options for CPU usage

   CPU is busy checking device status and cannot do other work correctly states CPU is busy polling and cannot perform other work effectively.

3. Final Answer:

   CPU is busy checking device status and cannot do other work -> Option B

4. Quick Check:

   Programmed I/O = CPU busy polling device [OK]

Hint: Programmed I/O keeps CPU busy waiting, no multitasking [OK]

Common Mistakes:

• Thinking CPU can multitask during programmed I/O
• Confusing interrupt-driven I/O effects with programmed I/O
• Assuming CPU ignores device in programmed I/O

4. A system uses interrupt-driven I/O but the CPU never responds to device interrupts. What is the likely problem?

medium

A. Interrupts are disabled or masked in the CPU

B. CPU is using programmed I/O instead

C. Device is not sending any interrupts

D. CPU is stuck in a loop polling the device

Solution

1. Step 1: Identify why CPU ignores interrupts

   If CPU never responds to interrupts, a common cause is that interrupts are disabled or masked, preventing CPU from handling them.

2. Step 2: Evaluate other options

   Interrupts are disabled or masked in the CPU correctly identifies this cause. Other options either contradict the interrupt-driven setup or describe different issues.

3. Final Answer:

   Interrupts are disabled or masked in the CPU -> Option A

4. Quick Check:

   CPU ignoring interrupts = interrupts disabled [OK]

Hint: CPU ignoring interrupts usually means interrupts are disabled [OK]

Common Mistakes:

• Assuming device is not sending interrupts
• Confusing programmed I/O with interrupt-driven I/O
• Thinking CPU polls device in interrupt-driven mode

5. A system designer wants to maximize CPU efficiency while handling multiple I/O devices. Which approach is best and why?

hard

A. Use programmed I/O because CPU controls all device checks

B. Use programmed I/O with longer polling intervals to reduce CPU load

C. Use interrupt-driven I/O so CPU works on other tasks until interrupted

D. Use neither; rely on manual device checks by the user

Solution

1. Step 1: Analyze CPU efficiency needs

   Maximizing CPU efficiency means CPU should not waste time waiting or polling devices unnecessarily.

2. Step 2: Compare I/O methods for efficiency

   Interrupt-driven I/O allows CPU to do other work and only respond when device signals, improving efficiency.

3. Step 3: Evaluate other options

   Programmed I/O wastes CPU cycles; manual checks are impractical. Longer polling reduces load but still wastes CPU time.

4. Final Answer:

   Use interrupt-driven I/O so CPU works on other tasks until interrupted -> Option C

5. Quick Check:

   Interrupt-driven I/O maximizes CPU efficiency [OK]

Hint: Interrupt-driven I/O lets CPU multitask efficiently [OK]

Common Mistakes:

• Choosing programmed I/O for efficiency
• Ignoring CPU multitasking benefits
• Thinking manual checks improve performance