Professional Documents
Culture Documents
Chap9 IO System
Chap9 IO System
fit@hcmus
fit@hcmus
2
fit@hcmus
I/O devices
£ Can be typify by: £ Character & Block devices
p Behavior: input, output, The device interface gives the illusion
storage that devices support the same API –
p Partner: human / machine character stream and block access
p Data rate: bytes/sec,
transfer/sec
3
fit@hcmus
I/O Modules
4
fit@hcmus
I/O Register Mapping
Memory Bus
£ Memory-mapped I/O
p Registers are addressed in Data Bus
same space as memory
p Address decoder distinguishes
between them
p OS uses address translation
mechanism to make them only
accessible to kernel
Memory I/O
I/O
6
fit@hcmus
7
fit@hcmus
I/O Data Transfer
8
fit@hcmus
9
fit@hcmus
10
fit@hcmus
I/O Commands
12
fit@hcmus
I/O Bus Types
£ Processor-Memory buses
p Short, high speed
p Design is matched to memory organization
£ I/O buses
p Longer, allowing multiple connections
p Connect to processor-memory bus through a
bridge
13
fit@hcmus
I/O Bus Example
Firewire USB 2.0 PCI Express Serial ATA Serial
Attached
SCSI
Intended use External External Internal Internal External
Devices per 63 127 1 1 4
channel
Data width 4 2 2/lane 4 4
Peak bandwidth 50MB/s or 0.2MB/s, 250MB/s/lan 300MB/s 300MB/s
100MB/s 1.5MB/s, or e
60MB/s 1×, 2×, 4×,
8×, 16×, 32×
Hot pluggable Yes Yes Depends Yes Yes
15
fit@hcmus
16
fit@hcmus
A. Behavior
B. Partner
C. Data rate
D. All of them
17
fit@hcmus
A. North Bridge
B. South Bridge
18
fit@hcmus
A. Programed I/O
B. Interrupt Driven I/O
C. Direct Memory Access
19
fit@hcmus
A. Port
B. Bus
C. Controller
20
fit@hcmus
21