1  1998 Morgan Kaufmann Publishers Chapter 8 Storage, Networks and Other Peripherals.

Slides:



Advertisements
Similar presentations
1 Lecture 22: I/O, Disk Systems Todays topics: I/O overview Disk basics RAID Reminder: Assignment 8 due Tue 11/21.
Advertisements

IT253: Computer Organization
I/O Chapter 8. Outline Introduction Disk Storage and Dependability – 8.2 Buses and other connectors – 8.4 I/O performance measures – 8.6.
CS224 Spring 2011 Computer Organization CS224 Chapter 6A: Disk Systems With thanks to M.J. Irwin, D. Patterson, and J. Hennessy for some lecture slide.
Princess Sumaya Univ. Computer Engineering Dept. Chapter 6:
Lecture 21Comp. Arch. Fall 2006 Chapter 8: I/O Systems Adapted from Mary Jane Irwin at Penn State University for Computer Organization and Design, Patterson.
1  1998 Morgan Kaufmann Publishers Interfacing Processors and Peripherals.
CPE 442 io.1 Introduction To Computer Architecture CpE 442 I/O Systems.
CSCE 212 Chapter 8 Storage, Networks, and Other Peripherals Instructor: Jason D. Bakos.
EE30332 Ch8 DP – 1 Ch 8 Interfacing Processors and Peripherals Buses °Fundamental tool for designing and building computer systems divide the problem into.
S. Barua – CPSC 440 CHAPTER 8 INTERFACING PROCESSORS AND PERIPHERALS Topics to be covered  How to.
Interfacing Processors and Peripherals Andreas Klappenecker CPSC321 Computer Architecture.
Other Disk Details. 2 Disk Formatting After manufacturing disk has no information –Is stack of platters coated with magnetizable metal oxide Before use,
Processor Design 5Z0321 Processor Design 5Z032 Chapter 8 Interfacing Processors and Peripherals Henk Corporaal.
11/18/2004Comp 120 Fall November 3 classes to go No class on Tuesday 23 November Last 2 classes will be survey and exam review Interconnect and.
1  1998 Morgan Kaufmann Publishers Chapter 8 Interfacing Processors and Peripherals.
1 Lecture 26: Storage Systems Topics: Storage Systems (Chapter 6), other innovations Final exam stats:  Highest: 95  Mean: 70, Median: 73  Toughest.
1 CSE SUNY New Paltz Chapters 8 Interfacing Processors and Peripherals.
1  2004 Morgan Kaufmann Publishers Chapters 8 & 9 (partial coverage)
1 Interfacing Processors and Peripherals I/O Design affected by many factors (expandability, resilience) Performance: — access latency — throughput — connection.
Prof. John Nestor ECE Department Lafayette College Easton, Pennsylvania ECE Computer Organization Lecture 22 - Input/Output.
Hard Disks and I/O Polytechnic University CS /25/03.
S.1 Review: Major Components of a Computer Processor Control Datapath Memory Devices Input Output Cache Main Memory Secondary Memory (Disk)
1  1998 Morgan Kaufmann Publishers Chapter Seven.
COMP381 by M. Hamdi 1 Input/Output Systems. COMP381 by M. Hamdi 2 Motivation: Who Cares About I/O? CPU Performance: 60% per year I/O system performance.
I/0 devices.
Computer Organization CS224 Fall 2012 Lesson 51. Measuring I/O Performance  I/O performance depends on l Hardware: CPU, memory, controllers, buses l.
Storage & Peripherals Disks, Networks, and Other Devices.
CS 352 : Computer Organization and Design University of Wisconsin-Eau Claire Dan Ernst Storage Systems.
CSE431 Chapter 6A.1Irwin, PSU, 2008 Chapter 6A: Disk Systems Mary Jane Irwin ( ) [Adapted from Computer Organization.
I/O – Chapter 8 Introduction Disk Storage and Dependability – 8.2 Buses and other connectors – 8.4 I/O performance measures – 8.6.
1 Chapter 7: Storage Systems Introduction Magnetic disks Buses RAID: Redundant Arrays of Inexpensive Disks.
Disk Access. DISK STRUCTURE Sector: Smallest unit of data transfer from/to disk; 512B 2/4/8 adjacent sectors transferred together: Blocks Read/write heads.
1 (Based on text: David A. Patterson & John L. Hennessy, Computer Organization and Design: The Hardware/Software Interface, 3 rd Ed., Morgan Kaufmann,
I/O Example: Disk Drives To access data: — seek: position head over the proper track (8 to 20 ms. avg.) — rotational latency: wait for desired sector (.5.
1  2004 Morgan Kaufmann Publishers Multilevel cache Used to reduce miss penalty to main memory First level designed –to reduce hit time –to be of small.
1 Chapter 2: Computer-System Structures  Computer System Operation  I/O Structure  Storage Structure  Storage Hierarchy  Hardware Protection  General.
Lecture 16: Storage and I/O EEN 312: Processors: Hardware, Software, and Interfacing Department of Electrical and Computer Engineering Spring 2014, Dr.
CS2100 Computer Organisation Input/Output (AY2010/2011) Semester 2 Adapted from.
Chapter 2: Computer-System Structures Computer System Operation I/O Structure Storage Structure Storage Hierarchy Hardware Protection Network Structure.
2.1 Operating System Concepts Chapter 2: Computer-System Structures Computer System Operation Storage Structure Storage Hierarchy Hardware Protection General.
I/O Computer Organization II 1 Introduction I/O devices can be characterized by – Behavior: input, output, storage – Partner: human or machine – Data rate:
Lecture 35: Chapter 6 Today’s topic –I/O Overview 1.
I/O Computer Organization II 1 Interconnecting Components Need interconnections between – CPU, memory, I/O controllers Bus: shared communication channel.
August 1, 2001Systems Architecture II1 Systems Architecture II (CS ) Lecture 9: I/O Devices and Communication Buses * Jeremy R. Johnson Wednesday,
Computer Organization CS224 Fall 2012 Lessons 47 & 48.
EEE440 Computer Architecture
CS2100 Computer Organisation Input/Output – Own reading only (AY2015/6) Semester 1 Adapted from David Patternson’s lecture slides:
Chapter 6 Storage and Other I/O Topics. Chapter 6 — Storage and Other I/O Topics — 2 Introduction I/O devices can be characterized by Behaviour: input,
1 Ó1998 Morgan Kaufmann Publishers Chapter 8 I/O Systems.
CS 6290 I/O and Storage Milos Prvulovic. Storage Systems I/O performance (bandwidth, latency) –Bandwidth improving, but not as fast as CPU –Latency improving.
1 Lecture 27: Disks Today’s topics:  Disk basics  RAID  Research topics.
1 Lecture 23: Storage Systems Topics: disk access, bus design, evaluation metrics, RAID (Sections )
Mohamed Younis CMCS 411, Computer Architecture 1 CMCS Computer Architecture Lecture 26 Bus Interconnect May 7,
10/15: Lecture Topics Input/Output –Types of I/O Devices –How devices communicate with the rest of the system communicating with the processor communicating.
1  2004 Morgan Kaufmann Publishers Page Tables. 2  2004 Morgan Kaufmann Publishers Page Tables.
Mohamed Younis CMCS 411, Computer Architecture 1 CMCS Computer Architecture Lecture 25 I/O Systems May 2,
Orange Coast College Business Division Computer Science Department CS 116- Computer Architecture Peripherals.
W4118 Operating Systems Instructor: Junfeng Yang.
LECTURE 13 I/O. I/O CANNOT BE IGNORED Assume a program requires 100 seconds, 90 seconds for main memory, 10 seconds for I/O. Assume main memory access.
Computer Organization & Design 计算机组成与设计 Weidong Wang ( 王维东 ) College of Information Science & Electronic Engineering 信息与通信工程研究所 Zhejiang.
CSCE 385: Computer Architecture Spring 2014 Dr. Mike Turi I/O.
Chapter 2: Computer-System Structures
Morgan Kaufmann Publishers Storage and Other I/O Topics
Virtual Memory Main memory can act as a cache for the secondary storage (disk) Advantages: illusion of having more physical memory program relocation protection.
Introduction I/O devices can be characterized by I/O bus connections
Lecture 13 I/O.
Input-output I/O is very much architecture/system dependent
CSC3050 – Computer Architecture
Presentation transcript:

1  1998 Morgan Kaufmann Publishers Chapter 8 Storage, Networks and Other Peripherals

2  1998 Morgan Kaufmann Publishers Introduction I/O Design affected by many factors (expandability, resilience) Three characteristics for organizing I/O devices –Behavior: input (read once), output (write only), or storage –Partner: Either a human or a machine is at the other end of the I/O device –Data rate: the peak rate at which data can be transferred between the I/O device and the main memory or processor.

3  1998 Morgan Kaufmann Publishers I/O Devices

4  1998 Morgan Kaufmann Publishers I/O Performance Performance: — access latency — throughput — connection between devices and the system — the memory hierarchy — the operating system A variety of different users (e.g., banks, supercomputers, engineers) each has different requirements.

5  1998 Morgan Kaufmann Publishers Typical Collection of I/O Devices

6  1998 Morgan Kaufmann Publishers Importance of I/O in a Networked Society Processors are being built from the same basic technology. I/O becomes one of the most distinctive features of the machines. As the importance of networking and information infrastructure grows, I/O plays an increasing important role.

7  1998 Morgan Kaufmann Publishers Impact of I/O on System Performance Suppose we have a benchmark that executes in 100 seconds of elapse time, where 90 seconds is CPU time and the rest is I/O time. If the CPU improves by 50% per year for the next five years but I/O time doesn’t improve, how much faster will our program run at the end of five years? Amdahl’s Law again!

8  1998 Morgan Kaufmann Publishers Assessing I/O Performance Depends on the application System throughput I/O bandwidth –how much data can we move through the system in a certain time? –How many I/O operations can we do per unit of time? Response time

9  1998 Morgan Kaufmann Publishers I/O Performance Measures Examples from Disk and File Systems affected by disk technology, how disk are connected, the memory, the processor, and the file system provided by the OS. Benchmark relatively primitive compared with those for the CPU. Note: transfer rate: 1 MB = 10^6 bytes, not 2^20 bytes Supercomputer I/O benchmarks: dominated by access to large files on magnetic disks. Data throughput, # of bytes per second that can be transferred between a supercomputer’s main memory and disks. Transaction Processing(TP) I/O benchmarks: –involve both response time requirement and a performance based on throughput. –Concerned with I/O rate, measured as # of disk accesses per second. –TPC has developed several benchmarks. File System I/O benchmarks: five phases --> Makedir, Copy, ScanDir, ReadAll, Make

10  1998 Morgan Kaufmann Publishers Disk Storage and Dependability Disk storage is nonvolatile, meaning that the data remains even when power is removed. Platters in hard disk are metal (or glass), offering several advantages over floppy disks: –can be larger because it is rigid –has higher density because it can be controlled more precisely –Has a higher data rate because it spins faster –can incorporate more platter

11  1998 Morgan Kaufmann Publishers I/O Example: Disk Drives 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) MB/sec

12  1998 Morgan Kaufmann Publishers Example For a disk rotating at 5400 RPM, average rotational latency = 0.5 rotation / 5400 RPM = 0.5 rotation/(5400 RPM/ 60) = 5.6ms For a disk rotating at 15,000 RPM, average rotational latency = 2.0ms Note: detailed control of the disk and the transfer between the disk and the memory is usually handled by a disk controller. The controller adds the final component of disk access time, controller time. The average time to perform an I/O operation will consist of these four times plus any wait time incurred because other processes are using the disk. Many recent disks have included caches directly in the disk to speed up the access time.

13  1998 Morgan Kaufmann Publishers Disk Read Time What is the average time to read or write a 512-byte sector for a typical disk rotating at 10,000 RPM? The advertised average seek time is 6 ms, the transfer rate is 50MB/sec, and the control overhead is 0.2ms. (Assuming no waiting time)

14  1998 Morgan Kaufmann Publishers Dependability, Reliability and Availability A system alternating between states: 1.Service accomplishment: where the service is delivered as specified 2.Service interruption: where the service is different from the specified service Transitions from state 1 to state 2 are caused by failures Transitions from state 2 to state 1 are called restorations. Reliability is a measure of the continuous service accomplishment. Mean-time-between-failures = Mean-time-to-failure + Mean-time-to- repair Availability = MTTF/(MTTF+MTTR)

15  1998 Morgan Kaufmann Publishers How to Increase MTTF Fault avoidance Fault tolerance Fault forecasting

16  1998 Morgan Kaufmann Publishers RAID Leveraging redundancy to improve the availability of disk storage is captured in the phrase: Redundant Array of Inexpensive Disks No redundancy (RAID 0): allocation of logically sequential blocks to separate disks to allow higher performance than a single disk can deliver Mirroring (RAID 1): writing the identical data to multiple disks to increase data availability. Error Detecting and Correcting Code (RAID 2) Bit-Interleaved Parity (RAID 3): Add enough redundant information to restore the lost information on a failure. Block-interleaved Parity (RAID 4) Distributed Block-interleaved Parity (RAID 5) P+Q redundancy (RAID 6)

17  1998 Morgan Kaufmann Publishers RAID 1-6

18  1998 Morgan Kaufmann Publishers Small Write Update on Raid 3 vs. Raid 4

19  1998 Morgan Kaufmann Publishers Networks Key characteristics of typical networks: –distance: 0.01 to 10,000 kilometers –speed: MB/sec to 1GBit/sec –topology: bus, ring, star, tree –shared lines: none (point-to-point) or shared RS232: slow but cheap LAN (ethernet): up to 1GBit/sec Ethernet is a bus with multiple masters and a scheme for determining who gets bus control. ATM: scalable network technology (155 Mbits/sec to 2.5 Gbits/sec) Example: Performance of two networks

20  1998 Morgan Kaufmann Publishers The OSI Model Layers

21  1998 Morgan Kaufmann Publishers TCP/IP Packet Format

22  1998 Morgan Kaufmann Publishers Performance of Two Networks Bandwidth 100 Mbit/s vs Mbit/s Interconnect latency: 10us HW latency from/to network: 2 us SW overhead sending to network: 100 us SW overhead receiving from network: 80 us Question: Find the host-to-host latency for a 250 byte message using each network.

23  1998 Morgan Kaufmann Publishers I/O Example: Buses Shared communication link (one or more wires) Difficult design: — may be bottleneck — length of the bus — number of devices — tradeoffs (buffers for higher bandwidth increases latency) — support for many different devices — cost Types of buses: — processor-memory (short high speed, custom design) — backplane (high speed, often standardized, e.g., PCI) — I/O (lengthy, different devices, standardized, e.g., SCSI)

24  1998 Morgan Kaufmann Publishers Bus: Connecting I/O Devices to Processor and Memory A bus generally contains a set of control lines and a set of data lines. Control lines are used to signal requests and acknowledges, and to indicate what type of information is on the data lines Data lines carry information between the source and the destination. The information may consist of data, complex commands or addresses. Bus transaction includes two parts: sending the address and receiving or sending the data. Read transaction == transfers data from memory Write transaction == writes data to the memory Input operation: input to memory so the processor can read it Output operation: output to device from memory

25  1998 Morgan Kaufmann Publishers Input Operation

26  1998 Morgan Kaufmann Publishers Different Machines using Different Types of Buses

27  1998 Morgan Kaufmann Publishers Synchronous and Asynchronous Buses Synchronous buses –use a clock and a synchronous protocol, fast and small –but every device must operate at same rate –clock skew requires the bus to be short –processor-memory buses are often synchronous Asynchronous buses –don’t use a clock and instead use handshaking –can accommodate a wide variety of devices

28  1998 Morgan Kaufmann Publishers Asynchronous Protocol Let’s look at some examples from the text “Performance Analysis of Synchronous vs. Asynchronous” “Performance Analysis of Two Bus Schemes”