Input/Output

73
1 Input/Output Chapter 5 5.1 Principles of I/O hardware 5.2 Principles of I/O software 5.3 I/O software layers 5.4 Disks 5.5 Clocks 5.6 Character-oriented terminals 5.7 Graphical user interfaces 5.8 Network terminals 5.9 Power management

description

Input/Output. 5.1 Principles of I/O hardware 5.2 Principles of I/O software 5.3 I/O software layers 5.4 Disks 5.5 Clocks 5.6 Character-oriented terminals 5.7 Graphical user interfaces 5.8 Network terminals 5.9 Power management. Chapter 5. I/O Device. - PowerPoint PPT Presentation

Transcript of Input/Output

Page 1: Input/Output

1

Input/Output

Chapter 5

5.1 Principles of I/O hardware5.2 Principles of I/O software5.3 I/O software layers5.4 Disks5.5 Clocks5.6 Character-oriented terminals5.7 Graphical user interfaces5.8 Network terminals5.9 Power management

Page 2: Input/Output

2

I/O Device

• I/O devices can be divided into two categories: – A block devices is one that stores information in

fixed-size blocks.– A character device delivers or accepts a stream of

characters, without regard to any block structure.

• Some devices do not fit in: clocks, memory-mapped screens.

Page 3: Input/Output

3

Principles of I/O Hardware

Some typical device, network, and data base rates

Page 4: Input/Output

4

Device Controllers

• I/O devices have components:– mechanical component – electronic component

• The electronic component is the device controller or adapter.– may be able to handle multiple devices– On PCs, it often takes the form of a printed circuit card

that can be inserted into an expansion slot.

• Controller's tasks– convert serial bit stream to block of bytes– perform error correction as necessary– make available to main memory

Page 5: Input/Output

5

Memory-Mapped I/O• Each controller ha a few registers that are used for

communicating with the CPU. The operating system can command the device by writing into these registers and learn the device’s state by reading from these registers.

• Many devices have a data buffer that the operating system can read and write. Two approaches exist:– Each control register is assigned an I/O port number.

– All the control registers are mapped into the memory space. This is called memory-mapped I/O.

Page 6: Input/Output

6

Memory-Mapped I/O

• Separate I/O and memory space• Memory-mapped I/O – PDP-11• Hybrid - Pentium

Page 7: Input/Output

7

Memory-Mapped I/O• Advantages of memory-mapped I/O:

– An I/O device driver can be written entirely in C – No special protection mechanism is needed to keep

user process from performing I/O. – Every instruction that can reference memory can

also reference control register.

• Disadvantages of memory-mapped I/O:– Caching a device control register would be

disastrous (not reflect current device status change).– All memory modules and all I/O devices must

examine all memory references.

Page 8: Input/Output

8

Memory-Mapped I/O

(a) A single-bus architecture(b) A dual-bus memory architecture

Page 9: Input/Output

9

Direct Memory Access (DMA)• Direct Memory Access (DMA) is a

capability provided by some computer bus architectures that allows data to be sent directly from an attached device (such as a disk drive) to the memory on the computer's motherboard.

• DMA operations:1. CPU program the DMA controller2. DMA requests transfer to memory3. Data transferred4. The disk controller sends an acknowledgement

Page 10: Input/Output

10

Direct Memory Access (DMA)

Operation of a DMA transfer

Page 11: Input/Output

11

Interrupts Revisited

• The interrupt vector is a table holding numbers on the address lines specifying devices.

• Precise interrupt:– The PC (Program Counter) is saved in a known place.

– All instructions before the one pointed to by the PC have fully executed.

– No instruction beyond the one pointed to by the PC has been executed.

– The execution state of the instruction pointed to by the PC is known.

Page 12: Input/Output

12

Interrupts Revisited

How interrupts happens. Connections between devices and interrupt controller actually use interrupt lines on the bus rather than dedicated wires

Page 13: Input/Output

13

Principles of I/O SoftwareGoals of I/O Software

• Device independence– programs can access any I/O device – without specifying device in advance

· (floppy, hard drive, or CD-ROM)

• Uniform naming– name of a file or device a string or an integer– not depending on which machine

• Error handling– handle as close to the hardware as possible

Page 14: Input/Output

14

Goals of I/O Software

• Synchronous vs. asynchronous transfers– blocking transfers vs. interrupt-driven– Most physical I/O is interrupt-driven.

• Buffering– data coming off a device cannot be stored in

final destination

• Sharable vs. dedicated devices– disks are sharable– tape drives would not be

Page 15: Input/Output

15

I/O Execution

• There are three ways that I/O are performed:– Programmed I/O

• Disadvantage: tying up the CPU full time until all the I/O is done.

– Interrupt-driven I/O• Interrupts might waste time.

– I/O using DMA• Slower than CPU

Page 16: Input/Output

16

Programmed I/O

• Steps in printing a string– String in the user buffer

– A System call to transfer the string to the kernel.

– String printed

Page 17: Input/Output

17

Programmed I/O

Writing a string to the printer using programmed I/O

Page 18: Input/Output

18

Interrupt-Driven I/O

• Writing a string to the printer using interrupt-driven I/O– Code executed when print system call is made– Interrupt service procedure

Page 19: Input/Output

19

I/O Using DMA

• Printing a string using DMA– code executed when the print system call is made– interrupt service procedure

Page 20: Input/Output

20

I/O Software Layers

• I/O Software in four layers:– Interrupt handlers– Device drivers– Device-independent operating system software– User-level I/O software

Page 21: Input/Output

21

I/O Software Layers

Layers of the I/O Software System

Page 22: Input/Output

22

Interrupt Handlers

• Interrupt handlers are best hidden– have driver starting an I/O operation block until

interrupt notifies of completion

• Interrupt procedure does its task– then unblocks driver that started it

Page 23: Input/Output

23

Interrupt Handlers

• Steps must be performed in software after interrupt completed

1. Save registers not already saved by interrupt hardware2. Set up context for interrupt service procedure3. Set up stack for interrupt service procedure4. Acknowledge interrupt controller, reenable

interrupts5. Copy registers from where saved6. Run service procedure 7. Set up MMU context for process to run next8. Load new process' registers9. Start running the new process

Page 24: Input/Output

24

Device Driver

• The device driver is the device-specific code for controlling the I/O device attached to a computer.

• Current operating systems expect drivers to fun in the kernel.

• Operating systems usually classify drivers into:– Block devices– Character devices

Page 25: Input/Output

25

Device Drivers

• Logical position of device drivers is shown here• Communications between drivers and device controllers goes over the

bus

Page 26: Input/Output

26

Device-Independent I/O Software

Functions of the device-independent I/O software

Uniform interfacing for device drivers

Buffering

Error reporting

Allocating and releasing dedicate devices

Providing a deice-independent block size

Page 27: Input/Output

27

Device-Independent I/O Software

(a) Without a standard driver interface – a lot of new programming effort

(b) With a standard driver interface

Page 28: Input/Output

28

Buffering

• Buffering is a widely-used technique. If data get buffered too many times, performance suffers.

• Classes of I/O errors:– Programming errors

– Actual I/O errors

• Some I/O software can be linked with user programs.– Spooling is a way of dealing with dedicated I/O devices in a

multiprogramming system.

– A spooling directory is used for storing the spooling jobs.

Page 29: Input/Output

29

Device-Independent I/O Software

(a) Unbuffered input(b) Buffering in user space(c) Buffering in the kernel followed by copying to user space(d) Double buffering in the kernel

Page 30: Input/Output

30

Device-Independent I/O Software

Networking may involve many copies

Page 31: Input/Output

31

User-Space I/O Software

Layers of the I/O system and the main functions of each layer

Page 32: Input/Output

32

Disks

• Disks come in a variety of types:– Magnetic disks (hard disks and floppy disks)– Arrays of disks– Optical disks

• CD-ROMs

• CD-Recordables

• CD-Rewritables

• DVD

Page 33: Input/Output

33

DisksDisk Hardware

Disk parameters for the original IBM PC floppy disk and a Western Digital WD 18300 hard disk

Page 34: Input/Output

34

Disk Hardware

• Physical geometry of a disk with two zones• A possible virtual geometry for this disk

Page 35: Input/Output

35

Disk Hardware

• Raid levels 0 through 2 • Backup and parity drives are shaded

Page 36: Input/Output

36

Disk Hardware

• Raid levels 3 through 5• Backup and parity drives are shaded

Page 37: Input/Output

37

Disk Hardware

Recording structure of a CD or CD-ROM

Page 38: Input/Output

38

Disk Hardware

Logical data layout on a CD-ROM

Page 39: Input/Output

39

Disk Hardware

• Cross section of a CD-R disk and laser– not to scale

• Silver CD-ROM has similar structure– without dye layer– with pitted aluminum layer instead of gold

Page 40: Input/Output

40

Disk Hardware

A double sided, dual layer DVD disk

Page 41: Input/Output

41

Disk Formatting

A disk sector

Page 42: Input/Output

42

Disk Formatting

An illustration of cylinder skew

Page 43: Input/Output

43

Disk Formatting

• No interleaving• Single interleaving• Double interleaving

Page 44: Input/Output

44

Disk Arm Scheduling Algorithms

• Time required to read or write a disk block determined by 3 factors

1. Seek time

2. Rotational delay

3. Actual transfer time

• Seek time dominates

• Error checking is done by controllers

Page 45: Input/Output

45

Disk Arm Scheduling Algorithms

Shortest Seek First (SSF) disk scheduling algorithm

Initialposition

Pendingrequests

Page 46: Input/Output

46

Disk Arm Scheduling Algorithms

The elevator algorithm for scheduling disk requests

Page 47: Input/Output

47

Error Handling

• A disk track with a bad sector• Substituting a spare for the bad sector• Shifting all the sectors to bypass the bad one

Page 48: Input/Output

48

Stable Storage

Analysis of the influence of crashes on stable writes

Page 49: Input/Output

49

ClocksClock Hardware

A programmable clock

Page 50: Input/Output

50

Clock Software (1)

Three ways to maintain the time of day

Page 51: Input/Output

51

Clock Software (2)

Simulating multiple timers with a single clock

Page 52: Input/Output

52

Soft Timers

• A second clock available for timer interrupts– specified by applications– no problems if interrupt frequency is low

• Soft timers avoid interrupts– kernel checks for soft timer expiration before it

exits to user mode– how well this works depends on rate of kernel

entries

Page 53: Input/Output

53

Character Oriented TerminalsRS-232 Terminal Hardware

• An RS-232 terminal communicates with computer 1 bit at a time

• Called a serial line – bits go out in series, 1 bit at a time

• Windows uses COM1 and COM2 ports, first to serial lines

• Computer and terminal are completely independent

Page 54: Input/Output

54

• Central buffer pool• Dedicated buffer for each terminal

Input Software (1)

Page 55: Input/Output

55

Input Software (2)

Characters handled specially in canonical mode

Page 56: Input/Output

56

Output Software

The ANSI escape sequences• accepted by terminal driver on output• ESC is ASCII character (0x1B)• n,m, and s are optional numeric parameters

Page 57: Input/Output

57

Display Hardware (1)

Memory-mapped displays• driver writes directly into display's video RAM

Parallel port

Page 58: Input/Output

58

Display Hardware (2)

• A video RAM image – simple monochrome display– character mode

• Corresponding screen– the xs are attribute bytes

Page 59: Input/Output

59

Input Software

• Keyboard driver delivers a number– driver converts to characters

– uses a ASCII table

• Exceptions, adaptations needed for other languages– many OS provide for loadable keymaps

or code pages

Page 60: Input/Output

60

Output Software for Windows (1)

Sample window located at (200,100) on XGA display

Page 61: Input/Output

61

Output Software for Windows (2)

Skeleton of a Windows main program (part 1)

Page 62: Input/Output

62

Output Software for Windows (3)

Skeleton of a Windows main program (part 2)

Page 63: Input/Output

63

Output Software for Windows (4)

An example rectangle drawn using Rectangle

Page 64: Input/Output

64

Output Software for Windows (5)

• Copying bitmaps using BitBlt.– before– after

Page 65: Input/Output

65

Output Software for Windows (6)

Examples of character outlines at different point sizes

Page 66: Input/Output

66

Network TerminalsX Windows (1)

Clients and servers in the M.I.T. X Window System

Page 67: Input/Output

67

X Windows (2)

Skeleton of an X Windows application program

Page 68: Input/Output

68

The SLIM Network Terminal (1)

The architecture of the SLIM terminal system

Page 69: Input/Output

69

The SLIM Network Terminal (2)

Messages used in the SLIM protocol from the server to the terminals

Page 70: Input/Output

70

Power Management (1)

Power consumption of various parts of a laptop computer

Page 71: Input/Output

71

Power management (2)

The use of zones for backlighting the display

Page 72: Input/Output

72

Power Management (3)

• Running at full clock speed

• Cutting voltage by two – cuts clock speed by two, – cuts power by four

Page 73: Input/Output

73

Power Management (4)

• Telling the programs to use less energy– may mean poorer user experience

• Examples– change from color output to black and white

– speech recognition reduces vocabulary

– less resolution or detail in an image