We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byLaura Malbon
Modified over 2 years ago
cs 152 buses.1 ©DAP & SIK 1995 CpE 242 Computer Architecture and Engineering Busses and OSs Responsibilities
cs 152 buses.2 ©DAP & SIK 1995 Recap: IO Benchmarks and I/O Devices °Disk I/O Benchmarks: Supercomputer Application: main concern is data rate Transaction Processing: main concern is I/O rate File System: main concern is file access °Three Components of Disk Access Time: Seek Time Rotational Latency: Transfer Time
cs 152 buses.3 ©DAP & SIK 1995 Outline of Todays Lecture °Recap and Introduction (5 minutes) ° Introduction to Buses (15 minutes) °Bus Types and Bus Operation (10 minutes) °Bus Arbitration and How to Design a Bus Arbiter (15 minutes) °Operating Systems Role (15 minutes) °Delegating I/O Responsibility from the CPU (5 minutes) °Summary (5 minutes)
cs 152 buses.4 ©DAP & SIK 1995 The Big Picture: Where are We Now? Control Datapath Memory Processor Input Output °Todays Topic: How to connect I/O to the rest of the computer? Control Datapath Memory Processor Input Output Network
cs 152 buses.5 ©DAP & SIK 1995 Buses: Connecting I/O to Processor and Memory °A bus is a shared communication link °It uses one set of wires to connect multiple subsystems Control Datapath Memory Processor Input Output
cs 152 buses.6 ©DAP & SIK 1995 Advantages of Buses °Versatility: New devices can be added easily Peripherals can be moved between computer systems that use the same bus standard °Low Cost: A single set of wires is shared in multiple ways Memor y Processor I/O Device
cs 152 buses.7 ©DAP & SIK 1995 Disadvantages of Buses °It creates a communication bottleneck The bandwidth of that bus can limit the maximum I/O throughput °The maximum bus speed is largely limited by: The length of the bus The number of devices on the bus The need to support a range of devices with: -Widely varying latencies -Widely varying data transfer rates Memor y Processor I/O Device
cs 152 buses.8 ©DAP & SIK 1995 The General Organization of a Bus °Control lines: Signal requests and acknowledgments Indicate what type of information is on the data lines °Data lines carry information between the source and the destination: Data and Addresses Complex commands °A bus transaction includes two parts: Sending the address Receiving or sending the data Data Lines Control Lines
cs 152 buses.9 ©DAP & SIK 1995 Master versus Slave °A bus transaction includes two parts: Sending the address Receiving or sending the data °Master is the one who starts the bus transaction by: Sending the address °Salve is the one who responds to the address by: Sending data to the master if the master ask for data Receiving data from the master if the master wants to send data Bus Master Bus Slave Master send address Data can go either way
cs 152 buses.10 ©DAP & SIK 1995 Output Operation °Output is defined as the Processor sending data to the I/O device: Processor Control (Memory Read Request) Memory Step 1: Request Memory I/O Device (Disk) Data (Memory Address) Processor Control Memory Step 2: Read Memory I/O Device (Disk) Data Processor Control (Device Write Request) Memory Step 3: Send Data to I/O Device I/O Device (Disk) Data (I/O Device Address and then Data)
cs 152 buses.11 ©DAP & SIK 1995 Input Operation °Input is defined as the Processor receiving data from the I/O device: Processor Control (Memory Write Request) Memory Step 1: Request Memory I/O Device (Disk) Data (Memory Address) Processor Control (I/O Read Request) Memory Step 2: Receive Data I/O Device (Disk) Data (I/O Device Address and then Data)
cs 152 buses.12 ©DAP & SIK 1995 Types of Buses °Processor-Memory Bus (design specific) Short and high speed Only need to match the memory system -Maximize memory-to-processor bandwidth Connects directly to the processor °I/O Bus (industry standard) Usually is lengthy and slower Need to match a wide range of I/O devices Connects to the processor-memory bus or backplane bus °Backplane Bus (industry standard) Backplane: an interconnection structure within the chassis Allow processors, memory, and I/O devices to coexist Cost advantage: one single bus for all components
cs 152 buses.13 ©DAP & SIK 1995 A Computer System with One Bus: Backplane Bus °A single bus (the backplane bus) is used for: Processor to memory communication Communication between I/O devices and memory °Advantages: Simple and low cost °Disadvantages: slow and the bus can become a major bottleneck °Example: IBM PC ProcessorMemory I/O Devices Backplane Bus
cs 152 buses.14 ©DAP & SIK 1995 A Two-Bus System °I/O buses tap into the processor-memory bus via bus adaptors: Processor-memory bus: mainly for processor-memory traffic I/O buses: provide expansion slots for I/O devices °Apple Macintosh-II NuBus: Processor, memory, and a few selected I/O devices SCCI Bus: the rest of the I/O devices ProcessorMemory I/O Bus Processor Memory Bus Bus Adaptor Bus Adaptor Bus Adaptor I/O Bus I/O Bus
cs 152 buses.15 ©DAP & SIK 1995 A Three-Bus System °A small number of backplane buses tap into the processor-memory bus Processor-memory bus is used for processor memory traffic I/O buses are connected to the backplane bus °Advantage: loading on the processor bus is greatly reduced ProcessorMemory Processor Memory Bus Bus Adaptor Bus Adaptor Bus Adaptor I/O Bus Backplane Bus I/O Bus
cs 152 buses.16 ©DAP & SIK 1995 Example Architecture: The SPARCstation 20 SPARCstation 20 Memory Controller Memory Bus Memory SIMMs Slot 1MBu s Slot 0MBu s MSBI Slot 1SBusSlot 0SBusSlot 3SBusSlot 2SBus MBus SECMACIO Disk Tape SCSI Bus SBus Keyboard & Mouse Floppy Disk External Bus
cs 152 buses.17 ©DAP & SIK 1995 The Underlying Network SPARCstation 20 Memory Controller Memory Bus MSBI Processor Bus: MBus SECMACIO Standard I/O Bus: Suns High Speed I/O Bus: SBus Low Speed I/O Bus: External Bus SCSI Bus
cs 152 buses.18 ©DAP & SIK 1995 USB °Universal Serial Bus Originally developed in 1995 by a consortium including -Compaq, HP, Intel, Lucent, Microsoft, and Philips USB 1.1 supports -Low-speed devices (1.5 Mbps) -Full-speed devices (12 Mbps) USB 2.0 supports -High-speed devices –Up to 480 Mbps (a factor of 40 over USB 1.1) -Uses the same connectors –Transmission speed is negotiated on device-by-device basis
cs 152 buses.19 ©DAP & SIK 1995 USB (contd) Hubs can be used to expand Upstream port Downstream ports
cs 152 buses.20 ©DAP & SIK 1995 Synchronous and Asynchronous Bus °Synchronous Bus: Includes a clock in the control lines A fixed protocol for communication that is relative to the clock Advantage: involves very little logic and can run very fast Disadvantages: -Every device on the bus must run at the same clock rate -To avoid clock skew, they cannot be long if they are fast °Asynchronous Bus: It is not clocked It can accommodate a wide range of devices It can be lengthened without worrying about clock skew It requires a handshaking protocol
cs 152 buses.21 ©DAP & SIK 1995 A Handshaking Protocol °Three control lines ReadReq: indicate a read request for memory Address is put on the data lines at the same line DataRdy: indicate the data word is now ready on the data lines Data is put on the data lines at the same time Ack: acknowledge the ReadReq or the DataRdy of the other party ReadReq AddressData Ack DataRdy
cs 152 buses.22 ©DAP & SIK 1995 Increasing the Bus Bandwidth °Separate versus multiplexed address and data lines: Address and data can be transmitted in one bus cycle if separate address and data lines are available Cost: (a) more bus lines, (b) increased complexity °Data bus width: By increasing the width of the data bus, transfers of multiple words require fewer bus cycles Example: SPARCstation 20s memory bus is 128 bit wide Cost: more bus lines °Block transfers: Allow the bus to transfer multiple words in back-to-back bus cycles Only one address needs to be sent at the beginning The bus is not released until the last word is transferred Cost: (a) increased complexity (b) decreased response time for request
cs 152 buses.23 ©DAP & SIK 1995 Obtaining Access to the Bus °One of the most important issues in bus design: How is the bus reserved by a devices that wishes to use it? °Chaos is avoided by a master-slave arrangement: Only the bus master can control access to the bus: It initiates and controls all bus requests A slave responds to read and write requests °The simplest system: Processor is the only bus master All bus requests must be controlled by the processor Major drawback: the processor is involved in every transaction Bus Master Bus Slave Control: Master initiates requests Data can go either way
cs 152 buses.24 ©DAP & SIK 1995 Multiple Potential Bus Masters: the Need for Arbitration °Bus arbitration scheme: A bus master wanting to use the bus asserts the bus request A bus master cannot use the bus until its request is granted A bus master must signal to the arbiter after finish using the bus °Bus arbitration schemes usually try to balance two factors: Bus priority: the highest priority device should be serviced first Fairness: Even the lowest priority device should never be completely locked out from the bus °Bus arbitration schemes can be divided into four broad classes: Distributed arbitration by self-selection: each device wanting the bus places a code indicating its identity on the bus. Distributed arbitration by collision detection: Ethernet uses this. Daisy chain arbitration: see next slide. Centralized, parallel arbitration: see next-next slide
cs 152 buses.25 ©DAP & SIK 1995 The Daisy Chain Bus Arbitrations Scheme °Advantage: simple °Disadvantages: Cannot assure fairness: A low-priority device may be locked out indefinitely The use of the daisy chain grant signal also limits the bus speed Bus Arbiter Device 1 Highest Priority Device N Lowest Priority Device 2 Grant Release Request
cs 152 buses.26 ©DAP & SIK 1995 Centralized Arbitration with a Bus Arbiter Arbiter Highest priority: ReqA Lowest Priority: ReqB Clk ReqA ReqB ReqC GrantA GrantB GrantC Clk ReqA ReqB GrA GrB
cs 152 buses.27 ©DAP & SIK 1995 Simple Implementation of a Bus Arbiter 3-bit D Register Clk ReqA ReqB ReqC Priority P0 P1 P2 G0 G1 G2EN SetGrA SetGrB SetGrC J K Clk J K J K Q Q Q ReqA ReqB ReqC GrantA GrantB GrantC
cs 152 buses.28 ©DAP & SIK 1995 Priority Logic EN P0 P1 P2 G0 G1 G2
cs 152 buses.29 ©DAP & SIK 1995 JK Flip Flop °JK Flip Flop can be implemented with a D-Flip Flop JKQ(t-1)Q(t) x0 10x D Q K J Q
cs 152 buses.30 ©DAP & SIK 1995 Simple Implementation of a Bus Arbiter 3-bit D Register Clk ReqA ReqB ReqC Priority P0 P1 P2 G0 G1 G2EN SetGrA SetGrB SetGrC J K Clk J K J K Q Q Q ReqA ReqB ReqC GrantA GrantB GrantC
cs 152 buses.31 ©DAP & SIK 1995 Responsibilities of the Operating System °The operating system acts as the interface between: The I/O hardware and the program that requests I/O °Three characteristics of the I/O systems: The I/O system is shared by multiple program using the processor I/O systems often use interrupts (external generated exceptions) to communicate information about I/O operations. -Interrupts must be handled by the OS because they cause a transfer to supervisor mode The low-level control of an I/O device is complex: -Managing a set of concurrent events -The requirements for correct device control are very detailed
cs 152 buses.32 ©DAP & SIK 1995 Operating System Requirements °Provide protection to shared I/O resources Guarantees that a users program can only access the portions of an I/O device to which the user has rights °Provides abstraction for accessing devices: Supply routines that handle low-level device operation °Handles the interrupts generated by I/O devices °Provide equitable access to the shared I/O resources All user programs must have equal access to the I/O resources °Schedule accesses in order to enhance system throughput
cs 152 buses.33 ©DAP & SIK 1995 OS and I/O Systems Communication Requirements °The Operating System must be able to prevent: The user program from communicating with the I/O device directly °If user programs could perform I/O directly: Protection to the shared I/O resources could not be provided °Three types of communication are required: The OS must be able to give commands to the I/O devices The I/O device must be able to notify the OS when the I/O device has completed an operation or has encountered an error Data must be transferred between memory and an I/O device
cs 152 buses.34 ©DAP & SIK 1995 Giving Commands to I/O Devices °Two methods are used to address the device: Special I/O instructions Memory-mapped I/O °Special I/O instructions specify: Both the device number and the command word -Device number: the processor communicates this via a set of wires normally included as part of the I/O bus -Command word: this is usually send on the buss data lines °Memory-mapped I/O: Portions of the address space are assigned to I/O device Read and writes to those addresses are interpreted as commands to the I/O devices User programs are prevented from issuing I/O operations directly: -The I/O address space is protected by the address translation
cs 152 buses.35 ©DAP & SIK 1995 I/O Device Notifying the OS °The OS needs to know when: The I/O device has completed an operation The I/O operation has encountered an error °This can be accomplished in two different ways: Polling: -The I/O device put information in a status register -The OS periodically check the status register I/O Interrupt: -Whenever an I/O device needs attention from the processor, it interrupts the processor from what it is currently doing.
cs 152 buses.36 ©DAP & SIK 1995 Polling: Programmed I/O °Advantage: Simple: the processor is totally in control and does all the work °Disadvantage: Polling overhead can consume a lot of CPU time CPU IOC device Memory Is the data ready? read data store data yes no done? no yes busy wait loop not an efficient way to use the CPU unless the device is very fast! but checks for I/O completion can be dispersed among computation intensive code
cs 152 buses.37 ©DAP & SIK 1995 Interrupt Driven Data Transfer °Advantage: User program progress is only halted during actual transfer °Disadvantage, special hardware is needed to: Cause an interrupt (I/O device) Detect an interrupt (processor) Save the proper states to resume after the interrupt (processor) add sub and or nop read store... rti memory user program (1) I/O interrupt (2) save PC (3) interrupt service addr interrupt service routine (4) CPU IOC device Memory :
cs 152 buses.38 ©DAP & SIK 1995 I/O Interrupt °An I/O interrupt is just like the exceptions except: An I/O interrupt is asynchronous Further information needs to be conveyed °An I/O interrupt is asynchronous with respect to instruction execution: I/O interrupt is not associated with any instruction I/O interrupt does not prevent any instruction from completion -You can pick your own convenient point to take an interrupt °I/O interrupt is more complicated than exception: Needs to convey the identity of the device generating the interrupt Interrupt requests can have different urgencies: -Interrupt request needs to be prioritized
cs 152 buses.39 ©DAP & SIK 1995 Interrupt Logic °Detect and synchronize interrupt requests Ignore interrupts that are disabled (masked off) Rank the pending interrupt requests Create interrupt microsequence address Provide select signals for interrupt microsequence Synchronizer Circuits Async interrupt requests Interrupt Mask Reg Interrupt Priority Network uSeq. addr & select logic DQ DQ Async. Inputs Sync. Inputs Clk : :
cs 152 buses.40 ©DAP & SIK 1995 Program Interrupt/Exception Hardware °Hardware interrupt services: Save the PC (or PCs in a pipelined machine) Inhibit the interrupt that is being handled Branch to interrupt service routine Options: -Save status, save registers, save interrupt information -Change status, change operating modes, get interrupt info. °A good thing about interrupt: Asynchronous: not associated with a particular instruction Pick the most convenient place in the pipeline to handle it
cs 152 buses.41 ©DAP & SIK 1995 Programmers View °Interrupt target address options: General: Branch to a common address for all interrupts Software then decode the cause and figure out what to do Specific: Automatically branch to different addresses based on interrupt type and/or level--vectored interrupt Add Sub Div main program Service the (keyboard) interrupt Save processor status/state Restore processor status/state (3) get PC interrupts request (e.g., from keyboard) (1) (2) Save PC and branch to interrupt target address
cs 152 buses.42 ©DAP & SIK 1995 Delegating I/O Responsibility from the CPU: DMA °Direct Memory Access (DMA): External to the CPU Act as a maser on the bus Transfer blocks of data to or from memory without CPU intervention CPU IOC device Memory DMAC CPU sends a starting address, direction, and length count to DMAC. Then issues "start". DMAC provides handshake signals for Peripheral Controller, and Memory Addresses and handshake signals for Memory.
cs 152 buses.43 ©DAP & SIK 1995 Delegating I/O Responsibility from the CPU: IOP CPU IOP Mem D1 D2 Dn... main memory bus I/O bus CPU IOP (1) Issues instruction to IOP memory (2) (3) Device to/from memory transfers are controlled by the IOP directly. IOP steals memory cycles. OP Device Address target device where cmnds are IOP looks in memory for commands OP Addr Cnt Other what to do where to put data how much special requests (4) IOP interrupts CPU when done
cs 152 buses.44 ©DAP & SIK 1995 Summary: °Three types of buses: Processor-memory buses I/O buses Backplane buses °Bus arbitration schemes: Daisy chain arbitration: it cannot assure fairness Centralized parallel arbitration: requires a central arbiter °I/O device notifying the operating system: Polling: it can waste a lot of processor time I/O interrupt: similar to exception except it is asynchronous °Delegating I/O responsibility from the CPU Direct memory access (DMA) I/O processor (IOP)
cs 152 buses.45 ©DAP & SIK 1995 Where to get more information? °Happy trail... Shing Kong 1047 Noel Dr., Apt. #4 Menlo Park, CA (w) °Until we meet again :-)
Cs 325 Bus.1 Bus Design. cs 325 Bus.2 What is a bus? °Slow vehicle that many people ride together well, true... °A bunch of wires...
Ceg3420 L17 Bus.1 DAP Fa97, U.CB CEG3420 Computer Design Lecture 18: Bus Design.
JR.S00 1 Lecture 15: Busses and Networking (1) Prof. Jan Rabaey Computer Science 252, Spring 2000 Based on slides from Dave Patterson, John Kubiatowicz.
CPEG3231 CPEG 323 Computer Architecture I/O Systems.
Lecture 21Comp. Arch. Fall 2006 Chapter 8: I/O Systems (continued) Adapted from Mary Jane Irwin at Penn State University for Computer Organization and.
Computer Buses For many of you who have depopulated his/her breadboards, THANKS! There are still some to be depopulated. Please dont forget to do it this.
1. OBJECTIVES: Defining the different types of buses Discussing bus arbitration and handshaking schemes Introducing I2C and PCI bus examples Interconnection.
SG 4: FIT1001 Computer Systems S Important Notice for Lecturers This file is provided as an example only Lecturers are expected to modify / enhance.
Chapter7. System Organization. System Organization - How computers and their major components are interconnected and managed at the system level. 7.1.
PCI Bus CENG Spring Dr. Yuriy ALYEKSYEYENKOV 2 The PCI (Peripheral Component Interconnect) bus was developed as a low-cost, processor-independent.
Buses – Page 1CSCI 4717 – Computer Architecture CSCI 4717/5717 Computer Architecture Topic: Buses Reading: Stallings, Sections 3.4, 3.5, and 7.7.
IT253: Computer Organization Lecture 13: Input/Output Tonga Institute of Higher Education.
1 Operating Systems Chapter 6. 2 What is an operating system? A program that runs on the hardware and supports Resource Abstraction Resource Sharing Abstracts.
1 Chapter 6 Operating Systems. 2 Learning outcomes Describe the functions of the Operating System and its components. Explain where the operating system.
Chapter 4 MARIE: An Introduction to a Simple Computer.
1 CSE 380 Computer Operating Systems Instructor: Insup Lee University of Pennsylvania Fall 2003 Lecture Notes: Multiprocessors (updated version)
Chapter 7 Input/Output Computer Organization and Architecture William Stallings 8th Edition.
Chapter 4: ISA 1 Chapter 4: Instruction Set Architectures CS140 Computer Organization These slides are derived from those of Null & Lobur + the work of.
Topics covered: Input/Output Organization CSE243: Introduction to Computer Architecture and Hardware/Software Interface.
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, output,
Computer Architecture & Operating Systems Workshop 2 - Lecture 1 Plagiarism & Citing Sources / Program Execution, Buses & I/O Devices.
What is an Operating System? A program that acts as an intermediary between a user of a computer and the computer hardware. Operating system goals: Execute.
Computer Architecture and Organization Computer Components and System Buses.
William Stallings Computer Organization and Architecture 8 th Edition Chapter 3 Top Level View of Computer Function and Interconnection.
Computer Architecture Lecture 31 Fasih ur Rehman.
Operating Systems Chapter 6. Main functions of an operating system 1. User/computer interface: Provides an interface between the user and the computer.
Computer Systems Lecturer: Szabolcs Mikulas URL: Textbook: W. Stallings,
ADAMA UNIVERSITY SCHOOL OF ENGENEERING & INFORMATION TECHNOLOGIES Sem. II,2010/11 INSTRUCTOR TARIKU W OPERATING SYSTEM (IT3016)
Chapter 6 System Integration and Performance. 2 Chapter Goals Implementation of the system bus and bus protocol. Interaction of the CPU with peripheral.
The I 2 C Bus. 2 of 40 The I 2 C Bus What is the I 2 C Bus and what is it used for? Bus characteristics I 2 C Bus Protocol Data Format Typical I 2 C devices.
© 2016 SlidePlayer.com Inc. All rights reserved.