admin
play

ADMIN Reading Chapter 8 Including RAID (8.2) but dont stress - PowerPoint PPT Presentation

ADMIN Reading Chapter 8 Including RAID (8.2) but dont stress memorizing the levels Can skip 8.8 IC220 Set #19: Storage and I/O (Chapter 8) 1 2 Big Picture I/O Interrupts Important but neglected Processor The


  1. ADMIN • Reading – Chapter 8 – Including RAID (8.2) but don’t stress memorizing the levels – Can skip 8.8 IC220 Set #19: Storage and I/O (Chapter 8) 1 2 Big Picture I/O Interrupts • Important but neglected Processor “The difficulties in assessing and designing I/O systems have often relegated I/O to second class status” Cache “courses in every aspect of computing, from programming to computer architecture often ignore I/O or give it scanty coverage” “textbooks leave the subject to near the end, making it easier Memory- I/O bus for students and instructors to skip it!” • GUILTY! Main I/O I/O I/O — we won’t be looking at I/O in much detail memory controller controller controller — be sure and read Chapter 8 carefully Network Graphics — Later – IC322: Computer Networks Disk Disk output 3 4

  2. Outline (A) I/O Overview • Can characterize devices based on: A. Overview 1. behavior B. Physically connecting I/O devices to Processors and Memory (8.4) C. Interfacing I/O devices to Processors and Memory (8.5) 2. partner (who is at the other end?) D. Performance Measures (8.6) E. Disk details/RAID (8.2) 3. data rate • Performance factors: — access latency — throughput — connection between devices and the system — the memory hierarchy — the operating system • Other issues: – Expandability, dependability 5 6 (B) Connecting the Processor, Memory, and other Devices (B) Bus Basics – Part 1 • Types of buses: Two general strategies: – Process-memory 1. Bus: ____________ communication link • Short, high speed, fixed device types Advantages: • custom design – I/O • lengthy, different devices Disadvantages: • Standards-based e.g., USB, Firewire Connect to proc-memory bus rather than directly to process • • Only one pair of devices (sender & receiver) may use bus at a time 2. Point to Point Network: ____________ links – Bus _______________ decides who gets the bus next based on Use switches to enable multiple connections some ______________ strategy Advantages: – May incorporate priority, round-robin aspects • Have two types of signals: Disadvantages: – “Data” – data or address 7 – Control 8

  3. I/O Bus Standards (B) Bus Basics – Part 2 • Today we have two dominant I/O bus standards: • Clocking scheme: 1. ____________________ Use a clock, signals change only on clock edge + Fast and small - All devices must operate at same rate - Requires bus to be short (due to clock skew) 2. ____________________ No clock, instead use “handshaking” + Longer buses possible + Accommodate wide range of device - more complex control 9 10 Handshaking example – CPU read from memory (C) Processor-to-device Communication How does CPU send information to a device? ReadReq 1 1. Special I/O instructions 3 x86: inb / outb Data 4 How to control access to I/O device? 2 6 2 4 Ack 5 2. Use normal load/instructions to special addresses 7 DataRdy Called ______________________ Load/store put onto bus 1. CPU requests read Memory ignores them (outside its range) 2. Memory acknowledges, CPU deasserts request Address may encode both device ID and a command 3. Memory sees change, deasserts Ack 4. Memory provides data, asserts DataRdy How to control access to I/O device? 5. CPU grabs data, asserts Ack 6. Memory sees Ack, deasserts DataRdy 7. CPU sees change, deasserts Ack 11 12

  4. (C) Device-to-processor communication DMA and Cache Coherency How does device get data to the processor? What could go wrong? Interrupts Processor 1. CPU periodically checks to see if device is ready: _________________ • CPU sends request, keep checking if done • Or just checks for new info (mouse, network) Cache Memory- I/O bus 2. Device forces action by the processor when needed: _________________ • Like an unscheduled procedure call • Same as “exception” mechanism that handles Main I/O I/O I/O TLB misses, divide by zero, etc. memory controller controller controller Network Graphics Disk Disk output 3. DMA: • Device sends data directly to memory w/o CPU’s involvement • Interrupts CPU when transfer is complete 13 14 (D) I/O’s impact on performance (D) Measuring I/O Performance • Total time = CPU time + I/O time • Latency? • Throughput? • Suppose our program is 90% CPU time, 10% I/O. If we improve CPU • Throughput with maximum latency? performance by 10x, but leave I/O unchanged, what will the new performance be? • Transaction processing benchmarks – TPC-C • Old time = 100 seconds – TPC-H • New time = – TPC-W • File system / Web benchmarks – “Make” benchmark – SPECSFS – SPECWeb 15 16

  5. (E) Disk Drives (E) RAID • _______________ ________________ _______________ ___________ Platters • Idea: lots of cheap, smaller disks • Small size and cost makes easier to add redundancy Tracks • Multiple disks increases read/write bandwidth Platter Sectors Track • To access data: — seek: position head over the proper track (3 to 14 ms. avg.) — rotational latency: wait for desired sector (.5 / RPM) — transfer: grab the data (one or more sectors) 30 to 80 MB/sec 17 18 RAID RAID RAID 0 – “striping”, no redundancy RAID 4 – Block-interleaved parity RAID 1 – mirrored RAID 5 – Distributed Block-interleaved Parity 19 20

  6. RAID Pentium 4 RAID 10 – Striped mirrors • I/O Options Pentium 4 processor System bus (800 MHz, 604 GB/sec) DDR 400 AGP 8X Memory (3.2 GB/sec) (2.1 GB/sec) Graphics controller Main output hub DDR 400 CSA memory (3.2 GB/sec) (north bridge) (0.266 GB/sec) DIMMs 1 Gbit Ethernet 82875P (266 MB/sec) Serial ATA Parallel ATA (150 MB/sec) (100 MB/sec) CD/DVD Disk Serial ATA Parallel ATA (150 MB/sec) (100 MB/sec) Tape Disk I/O AC/97 controller (1 MB/sec) hub • Key point – still need to do other backups (e.g. to tape) Stereo (south bridge) (surround- (20 MB/sec) 82801EB USB 2.0 10/100 Mbit Ethernet sound) – Provides protection from limited number of disk failures (60 MB/sec) PCI bus . . . – No protection from human failures! (132 MB/sec) 21 22 Fallacies and Pitfalls Fallacy: the rated mean time to failure of disks is 1,200,000 hours, • so disks practically never fail. • Fallacy: magnetic disk storage is on its last legs, will be replaced. • Fallacy: A 100 MB/sec bus can transfer 100 MB/sec. • Pitfall: Moving functions from the CPU to the I/O processor, expecting to improve performance without analysis. 23

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend