Unformatted text preview:

Recap Making address translation practical TLB Virtual memory memory acts like a cache for the disk CS152 Computer Architecture and Engineering Lecture 24 Page table maps virtual page numbers to physical frames Translation Look aside Buffer TLB is a cache translations virtual address Busses continued Queueing Theory Disk IO Virtual Address Space page Physical Memory Space off Page Table 2 0 November 28 2001 John Kubiatowicz http cs berkeley edu kubitron 1 3 physical address lecture slides http www inst eecs berkeley edu cs152 TLB page off frame page 2 2 0 5 11 28 01 CS152 Kubiatowicz Lec24 1 UCB Fall 2001 Recap Overlapped TLB Cache Access 11 28 01 CS152 Kubiatowicz Lec24 2 UCB Fall 2001 Recap A Three Bus System backside cache If we do this in parallel we have to be careful however Processor Memory Bus Processor Backside Cache bus assoc lookup 32 index TLB 4K Cache 10 2 disp 00 20 page 1K Bus Adaptor Bus Adaptor I O Bus L2 Cache Bus Adaptor I O Bus 4 bytes Hit Miss FN Memory FN Data Hit Miss A small number of backplane buses tap into the processor memory bus Processor memory bus is only used for processor memory traffic I O buses are connected to the backplane bus Advantage loading on the processor bus is greatly reduced What if cache size is increased to 8KB 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 3 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 4 Recap Main components of Intel Chipset Pentium II III Synchronous Bus Includes a clock in the control lines Northbridge Handles memory A fixed protocol relative to the clock Advantage little logic and very fast Disadvantages Graphics Southbridge I O PCI bus Disk controllers USB controlers 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 Audio Serial I O Interrupt controller It can be lengthened without worrying about clock skew It requires a handshaking protocol Timers 11 28 01 Recap Synchronous and Asynchronous Bus UCB Fall 2001 CS152 Kubiatowicz Lec24 5 Multiple Potential Bus Masters the Need for Arbitration 11 28 01 CS152 Kubiatowicz Lec24 6 UCB Fall 2001 Arbitration Obtaining Access to the Bus Bus arbitration scheme Control Master initiates requests 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 Master Data can go either way Bus Slave Bus arbitration schemes usually try to balance two factors One of the most important issues in bus design How is the bus reserved by a device that wishes to use it 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 Daisy chain arbitration Centralized parallel arbitration Distributed arbitration by self selection each device wanting the bus places a code indicating its identity on the bus Distributed arbitration by collision detection Each device just goes for it Problems found after the fact 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 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 7 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 8 The Daisy Chain Bus Arbitrations Scheme Device 1 Highest Priority Grant Device N Lowest Priority Device 2 Grant Centralized Parallel Arbitration Device 1 Grant Grant Release Bus Arbiter Device 2 Device N Req Bus Arbiter Request wired OR 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 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 9 Increasing the Bus Bandwidth 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 10 Increasing Transaction Rate on Multimaster Bus Separate versus multiplexed address and data lines Overlapped arbitration Address and data can be transmitted in one bus cycle if separate address and data lines are available perform arbitration for next transaction during current transaction Cost a more bus lines b increased complexity Bus parking master can holds onto bus and performs multiple transactions as long as no other master makes request Data bus width By increasing the width of the data bus transfers of multiple words require fewer bus cycles Example SPARCstation 20 s memory bus is 128 bit wide Overlapped address data phases prev slide requires one of the above techniques Cost more bus lines Split phase or packet switched bus Block transfers completely separate address and data phases arbitrate separately for each address phase yield a tag which is matched with data phase 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 11 28 01 Used in essentially all processor memory busses and in high speed I O busses UCB Fall 2001 All of the above in most modern buses CS152 Kubiatowicz Lec24 11 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 12 Administrivia What is DMA Direct Memory Access Typical I O devices must transfer large amounts of data to memory of processor Get going on Lab 7 Status update due Monday in Section Talk with Tas about the state of your project Disk must transfer complete block Large packets from network Regions of frame buffer DMA gives external device ability to access memory directly much lower overhead than having processor request one word at a time Midterm II on Friday 5 30 8 30 in 277 Cory Pizza afterwards Topics Issue Cache coherence What if I O devices write data that is currently in processor Cache The processor may never see new data Solutions Flush cache on every I O operation expensive Have hardware invalidate cache lines remember Coherence cache misses 11 28 01 CS152 Kubiatowicz Lec24 13 UCB Fall 2001 I O System Design Issues interrupts Cache Memory I O Bus Main Memory I O Controller Disk 11 28 01 Disk 11 28 01 UCB Fall 2001 CS152 Kubiatowicz Lec24 14 I O Device


View Full Document

Berkeley COMPSCI 152 - Lecture 24 Busses Queueing Theory Disk IO

Documents in this Course
Quiz 5

Quiz 5

9 pages

Memory

Memory

29 pages

Quiz 5

Quiz 5

15 pages

Memory

Memory

29 pages

Memory

Memory

35 pages

Memory

Memory

15 pages

Quiz

Quiz

6 pages

Midterm 1

Midterm 1

20 pages

Quiz

Quiz

12 pages

Memory

Memory

33 pages

Quiz

Quiz

6 pages

Homework

Homework

19 pages

Quiz

Quiz

5 pages

Memory

Memory

15 pages

Load more
Loading Unlocking...
Login

Join to view Lecture 24 Busses Queueing Theory Disk IO and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture 24 Busses Queueing Theory Disk IO and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?