Basic Course Information:
II. Historical Architectures
III. Instruction Level Parallelism
IV. Cache/Memory Hierarchy
V. I/O Architecture
VI. Other Interesting Architectures
| Class | Readings (Very approximate, at this point!) |
| April 2 | Introduction |
| April 4 | H&P 8.1-8.4, hw#1 due April 11 |
| April 9 | H&P 8.5, 8.6 |
| April 11 | H&P 8.7-8.11 |
| April 16 | The DASH Prototype: Logic Overhead and Performance. |
| April 18 | |
| April 23 | Memory Consistency in Shared Virtual Memory Systems,
Is SC + ILP = RC? |
| April 25 | Architecture and Applications of the HEP multiprocessor computing system,
The Tera Computer System, Exploiting Choice: Instruction Fetch and Issue on an Implementable Simultaneous Multithreading Processor |
| April 30 | Tera Hardware-Software Cooperation |
| May 2 | (1)Architecture of the IBM System/360
(2) Parallel Operation in the Control Data 6600 (3) The CRAY-1 Computer System (4) CRAY-1 Computer Technology also read pages 1-16 of the text (pages 1-55 in total) |
| May 7 | (1) Cramming More Components onto Integrated Circtuits,
(2) Two-Level Adaptive Training Branch Prediction |
| May 9 | (1) Combining
Branch Predictors
(2) The YAGS branch prediction scheme |
| May 14 | midterm |
| May 16 | (1) A Comparison of Full and Partial Predicated Execution Support for
ILP Processors
(2) Instruction Issue Logic for High-Performance, Interruptable Pipelined Processors (3) Highly accurate data value prediction using hybrid predictors |
| May 21 | (1) The
Alpha 21264 Microprocessor
(2) The MIPS R10000 Superscalar Microprocessor |
| May 23 | (1) Improving Direct-Mapped Cache ... (Jouppi)
(2) Organization and Performance of a Two-Level ... (Wang, Baer, Levy) |
| May 28 | Memorial Day Holiday |
| May 30 | (1) Trace
Cache: A Low Latency Approach to High Bandwidth Instruction Fetching
(2) Putting the fill unit to work: dynamic optimizations for trace cache microprocessors (3) Trace Processors |
| June 4 | (1) Multiscalar
Processors
(2) Threaded Multi-path Execution |
| June 6 | Project Presentations |
If you have comments or suggestions, email me at tullsen@cs.ucsd.edu