1. Chapter 13 – I/O Systems (Pgs 555-586 )

2. Devices  Two conflicting properties A. Growing uniformity in interfaces (both h/w and s/w): e.g., USB, TWAIN B. Growing disparity in device characteristics: e.g., haptic devices, speakers, monitors, plotters, network adapters

3. Device Categories  Various ways to categorise devices  Input: computer receives data  Output: computer sends data  Storage: data storage  Transmission : interdevice communication  Human Interface: HCI  Sensory: monitoring of conditions  Feedback: input in response to output ... etc...

4. Busses  A data communication path (wires) with a predefined protocol  A port is a connection to the bus  A controller, which is often has a separate processor and memory, may operate a port, bus, device, or some combination of them  The bus speed ("timing") is often different to the CPU clock speed, and is affected by the connection characteristics and bus length  PCIe (16GB) – Peripheral Component Interconnect, Express  SCSI – Small Computer System Interface  USB – Universal Serial Bus

5. A Typical PC Bus Structure

6. Controller IO  Controllers have registers  To send data to these registers, there are two communication methods 1. memory-mapped IO: registers mapped into the CPU's address space, i.e., use same address bus to access memory and IO devices 2. port-mapped IO: uses special CPU instructions (e.g., outb, outw), special IO lines, and perhaps an IO bus  Intel PCs use both methods

7. Ports  Typically have 4 registers 1. Data-In: to receive data, via the port 2. Data-Out: to send data out, via the port 3. Status: bits that describe the port's status 4. Control: bits to initiate IO, change mode, and perform operations

8. Port IO and Polling Host: 1. Read (status) busy bit until clear – "Polling" 2. Write byte into (data-out) register 3. Set (command) write bit 4. Set (command) command-ready bit Controller: 5. Set (status) busy bit 6. Interpret the (command) register 7. Do the command – transfer outgoing data 8. Clear (status) command-ready bit, error bit 9. Clear busy bit

9. Interrupts  Avoid need to poll devices  Uses special lines to the CPU, 2 Lines: 1. Maskable (for general IO) 2. Unmaskable for critical interrupts  Address bus usually contains offset into interrupt vector for interrupt handler  Interrupt lines checked after every CPU instruction cycle  Handlers are chained together if there are more handlers than vector slots (about 256)  Interrupts are typically given a priority level in case they are interrupted themselves (to see which one is executed)

10. Direct Memory Access (DMA)  Using CPU to move bytes from memory to IO port/controller is a waste of CPU time  Special controller (DMA Controller) serves as a CPU proxy and does the transfer to free-up the CPU  CPU cannot access memory while DMA controller has control of memory bus (but can use cache)

11. DMA Transfer

12. Device Drivers  OS Kernel has an IO subsystem  Device drivers abstract the details of the device so IO subsystem can have a common interface to devices  Permit H/W manufacturers more freedom  Extra layer between device controller and OS  OS specific so a device can work on many different platforms  ioctl() is generic and permits applications to interface with the device driver directly

13. Kernel IO Structure

14. IO Device Properties  Transfer Mode: character | block  Access Method: sequential | random  Transfer Schedule: a/synchronous  Sharing: dedicated | shared  Device Speed:  latency, seek time, transfer rate, inter-op delays, refresh cycle  Transfer Direction: read | write | read/write

15. Clocks and Timers  Systems have a built-in timer "clock" as a device – Variable Interval Timer  Can be programmed to provide an interrupt at a set time  Used by scheduler but also available for user processes  Based on counting clock cycles  Various hardware implementation methods

16. An IO request (blocking read) 1. Application calls read() 2. OS validates request, checks buffers (returns buffered data if possible) 3. Move process it device IO queue, IO scheduled for sending to device driver 4. Device driver requests space for result 5. Device driver has device perform data transfer 6. DMA controller (0r device) sends interrupt to say transfer of data complete 7. Interrupt handler sorts out what was happening and signals device driver that transfer is done 8. Device driver does post transfer actions and signals OS 9. OS unblocks process and runs scheduler

17. IO Requests

18. Performance  Lots of context switches to stress CPU and hardware caches  Considerable bus use for data transfer and buffering  Lots of interrupts, sometimes 3 or 4 per IO request  Fully exposes any weakness in the OS  One of the primary focuses of OS design

19. To Improve Performance  Reduce number of context switches  Reduce data transfers and copies  Reduce number of interrupts – larger transfers and more buffering  Increase concurrency – let controllers do more work  Move work into the hardware and controller

20. A New IO Algorithm

21. Operating Systems 1. Interrupt Mechanism 2. Processes/Threads + Scheduler 3. Interprocess Communication 4. Memory Management 5. IO Interfaces  Performance  Reliability

22. To Do:  Finish Assignment 3 (Due last day of classes)  Read Chapters 1 to 13 (The assigned course readings; all lectures)  Study for the Final Exam