Which statement correctly describes how the CPU is used in Programmed I/O compared to Interrupt-driven I/O?
Think about whether the CPU is busy checking the device or free to do other work.
Programmed I/O makes the CPU wait and check the device continuously, using CPU time actively. Interrupt-driven I/O lets the CPU do other work and only stops it when the device signals an interrupt.
What is the main disadvantage of using Programmed I/O compared to Interrupt-driven I/O?
Consider what happens when the CPU keeps checking the device repeatedly.
Programmed I/O wastes CPU time by constantly checking the device status, even when the device is not ready, leading to inefficiency.
How does Interrupt-driven I/O improve system responsiveness compared to Programmed I/O?
Think about how the CPU reacts to device readiness in both methods.
Interrupt-driven I/O lets the CPU continue other tasks and only stops it when the device signals readiness, improving responsiveness and efficiency.
Considering device speed and CPU efficiency, which I/O method is generally better for high-speed devices and why?
Think about how frequent device signals affect CPU workload in each method.
High-speed devices generate frequent signals; interrupt-driven I/O handles these efficiently by interrupting the CPU only when needed, avoiding constant polling.
In a multitasking operating system, what is a likely effect of using Programmed I/O instead of Interrupt-driven I/O?
Consider how CPU time spent polling affects the ability to run multiple tasks smoothly.
Programmed I/O wastes CPU cycles on polling, which reduces the CPU time available for other tasks, hurting multitasking performance.