Skip to main content

Chapter 7 · Watch, then practise

Input-Output Organization

Compare ways a CPU notices device work and moves data between devices and memory.

3 questions · 3 with related videos. Matches are based on playlist titles; broader background matches are labeled.

What to study

  • Polling
  • Interrupt service
  • Memory-mapped I/O
  • Direct memory access

Chapter playlists

Choose a playlist

Interrupt driven IO in Hindi | COA | Computer Organization and Architecture Lectures

Last moment tuitions · 11:47

Choose a video · 2 lectures

Compares interrupt-driven I/O with programmed I/O for the polling-versus-interrupt question.

1. Polling and interrupts

How does interrupt-driven input change the CPU’s work compared with polling?

Polling repeatedly reads device status. With interrupts, a device requests attention when service is needed; the CPU saves relevant state and enters a handler. The handler services the device and execution resumes. Interrupts reduce idle checking but introduce handling overhead and latency, so the best method depends on workload.

Memory Mapped IO vs IO Mapped IO in 8085 Microprocessor: Key Differences Explained

Engineering Funda · 9:14 · Background lecture

Introduces memory-mapped I/O using the 8085; device side effects and modern ordering requirements are explained below.

2. Memory-mapped I/O

Does a load from a memory-mapped device register behave like a load from ordinary RAM?

It uses the processor’s address space, but the selected address reaches device hardware. Reading can return status or consume input; writing can issue a command. Device registers therefore require the platform’s access and ordering rules. Treating them like freely cached ordinary data can produce incorrect behavior.

DMA Driven IO in Hindi | COA | Computer Organization and Architecture Lectures

Last moment tuitions · 13:44 · Background lecture

Explains DMA transfer background; this question’s CPU-virtual-address and DMA-mapping distinction is covered in the answer.

3. DMA addresses

Why should a device not simply receive a CPU virtual pointer as its DMA destination?

The device operates in a DMA or bus address space, which may differ from the CPU’s virtual and physical spaces. The driver prepares a buffer and obtains a suitable DMA mapping, then programs the device. DMA transfers data without the CPU copying each word, while software still manages setup, ownership and completion.

References