Scribd
Upload
79 views

CSCE 351 Operating System Kernels: Steve Goddard

This document discusses I/O hardware and software principles. It describes I/O devices like block and character devices. Device controllers interface with CPUs using techniques like memory-mapped I/O, I/O ports, and interrupt request lines. Direct memory access allows high-speed transfer of data between devices and memory. The goals of I/O software are device independence, uniform naming, and propagating errors close to hardware. Structured I/O software includes interrupt handlers, device drivers, and device-independent OS components to meet these goals.

Uploaded by

SrideviKumaresan
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
79 views

CSCE 351 Operating System Kernels: Steve Goddard

This document discusses I/O hardware and software principles. It describes I/O devices like block and character devices. Device controllers interface with CPUs using techniques like memory-mapped I/O, I/O ports, and interrupt request lines. Direct memory access allows high-speed transfer of data between devices and memory. The goals of I/O software are device independence, uniform naming, and propagating errors close to hardware. Structured I/O software includes interrupt handlers, device drivers, and device-independent OS components to meet these goals.

Uploaded by

SrideviKumaresan
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

CSCE 351 Operating System Kernels Principles of I/O Hardware and Software

Steve Goddard
[email protected]
http://www.cse.unl.edu/~goddard/Courses/CSCE351

I/O Hardware
x

I/O Devices
Block Devices Character Devices

Device Controllers
Memory-mapped I/O I/O Ports Interrupt Request Line (IRQ)

x x

Direct Memory Access (DMA) I/O Controllers and DMA


Disk Interleaving

I/O Devices
x

Block Devices
Information is stored and accessed in fixed-size blocks Block addressable, not byte addressable Common block sizes: 512 32,768 bytes Examples?

Character Devices
Send or receive streams of characters NOT byte or block addressable Examples?

What about
Tape drives? Clocks? Memory-mapped screens? Mice?
3

Device Controllers
x x

x x

Most I/O devices are electro-mechanical. The electrical component that interfaces with the CPU (actually the OS) is called the device controller or adapter. The Controller is the go-between for the OS and the device Controllers for PCs and embedded devices are implemented as daughter cards and inserted into the backplane of the parentboard (or motherboard)

Interfacing with Controllers


x

Memory-mapped I/O
Controller Registers are part of regular address space Usually flags in special registers indicate that the memory access is for memory-mapped I/O Used by Motorola 680x0 processors

x x

I/O Ports
Each controller is assigned a special address called a port.

Interrupt Request Lines (IRQ)


Physical input to the interrupt controller chip Signals when the device controller is ready to have its registers read/written via the I/O Ports (addresses) assigned that controller.

I/O Ports and IRQs


Example: PC with MS-DOS
I/O I/O address Controller Clock Keyboard Hard Disk Printer 040-043 060-063 1F0-1F7 378-37F Hardware IRQ 0 1 14 7 DOS Interrupt Vector 8 9 118 15 MINIX Interrupt Vector 40 41 54 47
6

Direct Memory Access (DMA)


x

Used mainly for block devices

Anatomy of a Disk
Basic components
Track s1 0 1 2
...

Block/Sector Head Cylinder

Surface Spindle

Platter

Anatomy of a Disk
Example: Seagate 9GB Fast/Wide/Differential SCSI disk
x

Specs: 12 platters 22 heads variable # of sectors/track 7,200 RPM


y

11 arms 4,735 tracks 512 bytes/sector

average latency: 4.2 ms. track-to-track: 1 ms average: 7.9 ms

Seek times
y y

40MB/s peak transfer rate

Disk Operations
Data transfer in units of sectors Random access devices with non-uniform access times
x x x x

Present disk with a sector address


DA = (drive, surface, track, sector)

Head moved to appropriate track


seek time

The appropriate head is enabled Wait for the sector to appear under the head
rotational latency

Read/write the sector


transfer time

10

Disk Interleaving
x

Blocks are often placed on the disk in nonsequential order to allow time for the DMA buffer to be transferred to main memory.

No interleaving

Single interleaving

Double interleaving
11

I/O Software
x x

Goals of I/O Software Structured I/O Software


Interrupt Handlers Device Drivers Device-Independent I/O SW User-Space I/O SW

12

Goals of I/O Software


x

Device independence
Read and Write from Floppy, Disk, CD-ROM without modifying programs Names are not dependent on the specific device
y

Uniform naming

Different devices of same type have similar name

In UNIX, all I/O is integrated with the file system Propagate errors up only when lower layer cannot handle it. Hide errors as much as possiblemany HW errors are transient Most I/O hardware operates asynchronously Synchronous (blocking) read/write easier to program
13

Error handling done as close to HW as possible


Synchronous read/write at application level


Structured I/O SW to meet Goals


x

Structured I/O SW to meet these Goals User-level Software Device-Independent OS SW Device Drivers Interrupt Handlers

14

Interrupt Handlers
x x

Hidden from applications Used to bridge gap between asynchronous I/O hardware and synchronous read/write semantics Often implemented as top-half and bottom-half handlers
Top-half
y y

does as little as possible not scheduled closely related to (if not exactly) the device driver scheduled

Bottom-half
y y

15

Device Drivers
x x x

Device dependent code Each device driver handles (at most) one class of devices Device drivers communicate with the device controllers
Only part that knows the details of the device. Hence, device dependent

Translate device-independent (abstract) requests to device-specific commands

16

Device Driver
Block to Sector Mappings
Surface

?
Sector

Track

Device driver translates block requests into cylinder, track, and sector requests.

t1 ... p1 ... 1 0

1 0
...

s1 0 1

17

Device-Independent I/O Software


x

Functions of device-independent I/O SW


Uniform interfacing for device drivers Device naming
y

Mnemonic names mapped to Major and Minor device numbers

Device protection Providing a device-independent block size Buffering Storage allocation on block devices Allocation and releasing dedicated devices Error Reporting

In MINIX, most device-independent I/O SW is in the file system (layer 3).


18

User-Space I/O SW
x

I/O Libraries (e.g., stdio) are in user-space to provide an interface to the OS resident device-independent I/O SW
These routines do the formatting for the user that is such a pain to do, but everyone wants it

Simultaneous Peripheral Operations On-Line (Spooling)


A user-space print command puts a file in the spooling directory and then asks a daemon process to execute the I/O request Printing is one use of spooling. Others? Why spool I/O?

19

Putting It All Together

20

You might also like