Input/Output Systems

Transcription

1 CSE325 Principles of Operating Systems Input/Output Systems David P. Duggan April 2, 2013

2 Input/Output Devices Output Device Input Device Processor 4/2/13 CSE325 - I/O Systems 2

3 Why we care about I/O? CPU Performance: 50% to 100% improvement per year I/O system performance limited by mechanical delays < 5% per year (IO per sec or MB per sec) Amdahl's Law: system speed-up limited by the slowest part! 10% IO & 10x CPU 5x Performance (lose 50%) 10% IO & 100x CPU 10x Performance (lose 90%) I/O bottleneck: Diminishing fraction of time in CPU Diminishing value of faster CPUs 4/2/13 CSE325 - I/O Systems 3

4 I/O Systems 4/2/13 CSE325 - I/O Systems 4

5 A Typical PC Motherboard 4/2/13 CSE325 - I/O Systems 5

6 A Typical PC Bus Structure 4/2/13 CSE325 - I/O Systems 6

7 Device I/O Port Locations on PCs (partial) 4/2/13 CSE325 - I/O Systems 7

8 The Device Driver Interface write( ); Abstract Software Interfaces Device Interface Terminal Driver Printer Driver Disk Driver Terminal Controller Printer Controller Disk Controller 4/2/13 CSE325 - I/O Systems 8

9 Device Management Organization System Interface Application Process File Manager Hardware Interface Device-Independent Device-Dependent Why 2 layers? Command Status Data Device Controller 4/2/13 9

10 A Kernel I/O Structure 4/2/13 10

11 Trap Table Device Independent Function Call func i ( ) dev_func_i(devid, ) { // Processing common to all devices switch(devid) { case dev0: dev0_func_i( ); break; case dev1: dev1_func_i( ); break; case devm: devm_func_i( ); break; }; // Processing common to all devices } 4/2/13 11

12 System Call Interface Functions available to application programs Abstract all devices (and files) to a few interfaces Make interfaces as similar as possible Block vs character Sequential vs direct access Device driver implements functions (one entry point per API function) open Prepare dev for operation close No longer using the device ioctl Character dev specific info read Character dev input op write Character dev output op strategy Block dev input/output ops select Character dev check for data stop Discontinue a stream output op 4/2/13 12

13 Operation of a Device... read(dev_i, %d, x); y = f(x) startread(dev_i, %d, x);... While(stillReading()) ; y = f(x)... Data on device Problem? Variable x Register Device dev_i Memory CPU 4/2/13 13

14 Overlapping Processing and I/O App 1 App 2 I/O Ctlr t 1 t 2 t 3 t 4 4/2/13 CSE325 - I/O Systems 14

15 Overlapping CPU-Controller Operations in a Process App I/O Ctlr t 1 t 2 t 3 t 4 t 5 t 6 t 7 t 8 t 9 4/2/13 CSE325 - I/O Systems 15

16 Polling I/O Read Operation read(device, ); System Interface 1 Data read function write function 5 Is there a performance problem? Low CPU utilization Hardware Interface Command Status Data Device Controller 4/2/13 CSE325 - I/O Systems 16

17 Interrupt-driven I/O Operation 1 System Interface read(device, ); Data 9 8b Device Status Table 3 2 read driver write driver 4 7 Device Handler Interrupt Handler 6 8a Hardware Interface 5 Command Status Data Device Controller 4/2/13 CSE325 - I/O Systems 17

18 Handling Interrupts Device driver J int read( ) { // Prepare for I/O save_state(j); out dev# // Done (no return) } Device status table J Device interrupt handler J void dev_handler( ) { get_state(j); //Cleanup after op signal(dev[j]); return_from_sys_call(); } Interrupt Handler Device Controller 4/2/13 CSE325 - I/O Systems 18

19 Handling Interrupts(2) Device driver J int read( ) { out dev# // Return after interrupt wait(dev[j}); return_from_sys_call(); } Device interrupt handler J void dev_handler( ) { //Cleanup after op signal(dev[j]); } Interrupt Handler Device Controller 4/2/13 CSE325 - I/O Systems 19

20 Intel Pentium Processor Event- Vector Table 4/2/13 20

21 Direct Memory Access Used to avoid programmed I/O for large data movement Requires DMA controller Bypasses CPU, transfers data directly between I/O device and memory 4/2/13 CSE325 - I/O Systems 21

22 Six Step Process to Perform DMA Transfer 4/2/13 CSE325 - I/O Systems 22

23 Characteristics of I/O Devices 4/2/13 CSE325 - I/O Systems 23

24 Block and Character Devices Block devices, e.g., disk drives Commands include read, write, seek Raw I/O or file-system access Memory-mapped file access possible Character devices, e.g., keyboards, mice, serial ports Commands include get, put Libraries layered on top allow line editing 4/2/13 CSE325 - I/O Systems 24

25 Blocking and Nonblocking I/O Blocking - process suspended until I/O completed Easy to use and understand Insufficient for some needs Nonblocking - I/O call returns as much as available User interface, data copy (buffered I/O) Implemented via multi-threading Returns quickly with count of bytes read or written Asynchronous - process runs while I/O executes Can be difficult to use I/O subsystem signals process when I/O completed 4/2/13 CSE325 - I/O Systems 25

26 Two I/O Methods Synchronous" Asynchronous" 4/2/13 CSE325 - I/O Systems 26

27 Kernel I/O Subsystem Scheduling Some I/O requests ordered via per-device queue Some OSs try fairness Priority of VM subsystem over app requests Buffering - store data in memory while transferring between devices To cope with device speed mismatch To cope with device transfer size mismatch To maintain copy semantics 4/2/13 CSE325 - I/O Systems 27

28 Device-status Table 4/2/13 CSE325 - I/O Systems 28

29 Error Handling OS must recover from disk read, device unavailable, transient write failures Most return an error number or code when I/O request fails System error logs hold problem reports 4/2/13 CSE325 - I/O Systems 29

30 I/O Protection User process may accidentally or purposefully attempt to disrupt normal operation via illegal I/O instructions All I/O instructions defined to be privileged I/O must be performed via system calls Database? Memory-mapped and I/O port memory locations must be protected too 4/2/13 CSE325 - I/O Systems 30

31 System Call Use to Perform I/O 4/2/13 31

32 Kernel Data Structures Kernel keeps state info for I/O components, including open file tables, network connections, character device state Many, many complex data structures to track buffers, memory allocation, dirty blocks Some use object-oriented methods and message passing to implement I/O 4/2/13 CSE325 - I/O Systems 32

33 UNIX I/O Kernel Structure 4/2/13 CSE325 - I/O Systems 33

34 I/O Requests to Hardware Operations Consider reading a file from disk for a process: Determine device holding file Translate name to device representation Physically read data from disk into buffer Make data available to requesting process Return control to process 4/2/13 CSE325 - I/O Systems 34

35 Life Cycle of An I/O Request 4/2/13 CSE325 - I/O Systems 35

36 Performance I/O a major factor in system performance: Demands CPU to execute device driver, kernel I/O code Context switches due to interrupts Data copying Network traffic especially stressful 4/2/13 CSE325 - I/O Systems 36

37 Improving Performance Reduce number of context switches Reduce data copying Reduce interrupts by using large transfers, smart controllers, polling Use DMA Balance CPU, memory, bus, and I/O performance for highest throughput 4/2/13 CSE325 - I/O Systems 37

38 Hardware Buffering Process Process Process Controller Controller Controller Data A B A B Device Device Device Unbuffered Process reads b i-1 Controller reads b i Process reads b i Controller reads b i+1 4/2/13 38