This document provides an overview of the key topics and objectives covered in a computer architecture course. The course aims to evaluate instruction set design tradeoffs, advanced pipelining techniques, solutions to increasing memory latency, and qualitative and quantitative tradeoffs in modern computer system design. Key areas covered include instruction set architecture, memory hierarchies, pipelining, parallelism, and performance evaluation metrics.

1. CIS775: Computer Architecture Chapter 1: Fundamentals of Computer Design

4. Computer Architecture Topics Instruction Set Architecture Pipelining, Hazard Resolution, Superscalar, Reordering, Prediction, Speculation, Vector, DSP Addressing, Protection, Exception Handling L1 Cache L2 Cache DRAM Disks, WORM, Tape Coherence, Bandwidth, Latency Emerging Technologies Interleaving Memories RAID VLSI Input/Output and Storage Memory Hierarchy Pipelining and Instruction Level Parallelism

5. Computer Architecture Topics M Interconnection Network S P M P M P M P ° ° ° Topologies, Routing, Bandwidth, Latency, Reliability Network Interfaces Shared Memory, Message Passing, Data Parallelism Processor-Memory-Switch Multiprocessors Networks and Interconnections

10. Growth in Microprocessor Performance

11. Six Generations of DRAMs

16. Computer Engineering Methodology Evaluate Existing Systems for Bottlenecks Simulate New Designs and Organizations Implement Next Generation System Technology Trends Benchmarks Workloads Implementation Complexity

20. Metrics of Performance Compiler Programming Language Application Datapath Control Transistors Wires Pins ISA Function Units (millions) of Instructions per second: MIPS (millions) of (FP) operations per second: MFLOP/s Cycles per second (clock rate) Megabytes per second Answers per month Operations per second

22. After putting in a blazing performance on the benchmark test, Sun issued a glowing press release claiming that it had outperformed Windows NT systems on the test. Pendragon president Ivan Phillips cried foul, saying the results weren't representative of real-world Java performance and that Sun had gone so far as to duplicate the test's code within Sun's Just-In-Time compiler . That's cheating, says Phillips, who claims that benchmark tests and real-world applications aren't the same thing. Did Sun issue a denial or a mea culpa? Initially, Sun neither denied optimizing for the benchmark test nor apologized for it. " If the test results are not representative of real-world Java applications, then that's a problem with the benchmark ," Sun's Brian Croll said. After taking a beating in the press, though, Sun retreated and issued an apology for the optimization.[Excerpted from PC Online 1997]

25. SPEC 2000 (CINT 2000)Results

26. SPEC 2000 (CFP 2000)Results

34. Amdahl’s Law ExTime new = ExTime old x (1 - Fraction enhanced ) + Fraction enhanced Speedup overall = ExTime old ExTime new Speedup enhanced = 1 (1 - Fraction enhanced ) + Fraction enhanced Speedup enhanced

38. Example: Calculating CPI Typical Mix Base Machine (Reg / Reg) Op Freq Cycles CPI(i) (% Time) ALU 50% 1 .5 (33%) Load 20% 2 .4 (27%) Store 10% 2 .2 (13%) Branch 20% 2 .4 (27%) 1.5