1 / 20

Introduction to Computer Architecture CSE 520 Fall 2007

Introduction to Computer Architecture CSE 520 Fall 2007. Sandeep K. S. Gupta Arizona State University. Computer Architect(ure)?. CA = ISA + O + H ISA – Instruction Set Architecture O – Organization H - Hardware Computer architect design a computer to meet functional requirements AND

zariel
Download Presentation

Introduction to Computer Architecture CSE 520 Fall 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Computer Architecture CSE 520 Fall 2007 Sandeep K. S. Gupta Arizona State University

  2. Computer Architect(ure)? • CA = ISA + O + H • ISA – Instruction Set Architecture • O – Organization • H - Hardware • Computer architect design a computer • to meet functional requirements AND • to meet price, performance and availability goals

  3. Motivational Quote • “It is not a dreary science of paper machines that will never work. No! It’s a discipline of keen intellectual interest, requiring the balance of marketplace forces to cost-performance-power, leading to glorious failures and some notable successes.” – HP, CAaQA 1st ed.

  4. Course Goals • To build upon the understanding of fundamentals of instruction set design, quantative principles of CA, processor design to exploit parallelism (ILP, TLP, DLP), memory-hierarchy design, storage system design in-order to understand the current trends in CA: • shift from single processor (core) chips to multiprocessor on chips (multi-core) to optimize performance/watts, • increasing focus on dependability – to address more hard/soft errors at smaller feature sizes < 65nm. • Embedded – low-power and thermal-aware design • Increased focus on server consolidation and virtualization • To get an idea of future of CA

  5. Course Goals - Indirect • To get you a high-paying job • To enrich you with new ideas • To train you in systems oriented thinking • To prepare you for research/profession in computer architecture – but more generally – in computer systems (CA+Compiler+OS+Application)

  6. Course Pre-req • CSE 230 (new) – Computer Organization and Assembly Language Programming http://cse.asu.edu/courses/descriptions/230.php • CSE 330 (old) – Computer Organization, CSE 225 – Assembly Language programming • CSE 420: UG Computer Architecture • Knowledge of C and Assembly Language Programming

  7. That is … • CSE420+230/330 Goal 1 “To provide an exposure to the organization and implementation of a computer system at the hardware level.” • The student can identify the five major components of a computersystem and describe how the components interact and the effect on the system as a whole. • The student can describe data representation, the instruction set, addressing modes, and register organization. • The student can describe the execution of instructions, and the hardware components used in each step. • The student can identify several approaches to processor implementations: Single cycle, Multi-cycle, Pipelined, Superscalar • The students can describe various memory organizations including virtual memory and cache organization structures • The student can describe what busses are and describe their role in connecting the major system components. • The student can describe how processor identifies different sources of interruptsand exceptions and invokes the corresponding handler to deal with the interrupt or exception.

  8. That is … (Cont.) • CSE420+230/330 Goal 2 “To develop an introductory understanding of assembly language and the relationship between computer hardware and machine code/assembly code.” • The student can develop assembly language programs that include flow control constructs (sequential, conditional and iterative). • The student can develop assembly language programs, including subroutines employing modularity, readability and reliability principles. • The student can develop assembly-language programs that use the stack to save register contents, pass parameters to subroutines, and create stack frames for local variables. • The student can develop abasic interrupt handler routine • The student can develop a basic IO handler routine

  9. That is … (Cont.) • CSE 420+230/330 Goal 3: “To develop the tools necessary to analyze the performance of computer architecture and organization.” • The student can identify various metrics to evaluate the performance of computer systems. • The student can evaluate memory cache performance • The student can identify several I/O performance measures.

  10. PreReq: Fallacies and Pitfalls • Fallacy: “Pre-req don’t matter, I am smart enough to pick it up during semester.” • Fallacy: “Instructor doesn’t care about Pre-req.” • Pitfall: Attempting to do assignments and exams without getting sound grasp on pre-req material

  11. Course/Reference Book(s) + Material • Computer Architecture: A Quantitative Approach (Fourth Edition) by John L. Hennessy and David A. Patterson • Reading List on the course web site • Reference: • Computer Organization and Design: The Hardware Software Interface, Patterson and Hennessy • Parallel Computer Architecture: A hardware/software approach.

  12. Topics – tentative list • Background/Pre-req topics: • ISA: IS Principles and Architectures (App-B) and Survey of IS A (App-J) – self-reading • ILP: Pipelining: Basic, Intermediate Concepts (App-A), ILP & its exploitation (Ch2), Limits of ILP (Ch 3) – self-reading + overview/covered in class as needed • Memory Hierarchy: Review of MH (App-C), MH Design (Ch-5), Storage Systems (Ch-6) – self-reading + overview/covered in class as needed • Main Topic: Covered through papers + lectures etc. • Quantative Principles of Computer Design (Ch1). • TLP, DLP: Multiprocessor and Thread-Level Parallelism (Ch-4) – multicore, system-on-chip, cell-architecture, clusters, Shared/distributed-memory multiprocessor, GPUs etc. • Embedded Systems (A-D), Interconnection Networks (A-E) • Thermal/Power-aware architecture (low-power arch.) • Support for Virtualization and other features.

  13. Course Mechanics • Homeworks+Exams+Quizzes: 30% • Exams – take home • Homeworks – may involve programming • Quizzes – may be un-announced • Paper presentation: 40% • Presentation, critiquing, discussion (online Google group), summary • Term Project • Group • Self-defined (with help of instructor) • Involves analysis/implementation

  14. Class Format • Lecture (5-75 min) • As class progresses the lecture time will decrease (on average) • One or Two Paper presentation (1/2 hr each) • Starting soon! • 5 min. mid-break – if desired • Note: slides of presenters should be provided to TA one day in advance.

  15. Class Cyberpresence • http://impact.asu.edu/~mcn/cse520fa07.html • class assignments • Solutions • Slides • reference material • Visit regularly for latest information

  16. What can you expect from this course? • Lots of in-class/ on-line interaction • Interesting and challenging assignments and exam questions • Reading technical papers – classical as well as state-of-art • Technical Writing – critiquing, summarizing • Help/Tutorials by instructor/TA on difficult material • And lot more!

  17. Contacting Me or TA • Instructor • Email: sandeep.gupta@asu.edu • Subject line: CSE520Fa07 • Office: BY 522 • Phone: 5-3806 • Office Hours: T-TH 4:30-6pm • Call me || come to my office hrs || Set up an appointment • http://impact.asu.edu • TA Guofeng Deng • Email: guofeng.deng@asu.edu • Office BY517AE • Office Hours: W 2-5pm or by appointment

  18. What do I do when I am not teaching?

  19. Thermal Management for Data Centers Pervasive Health Monitoring Criticality Aware-Systems Mobile Ad-hoc Networks ID Assurance • Goal: • Increasing computing capacity for datacenters • Energy efficiency • Features: • Online thermal evaluation • Thermal Aware Scheduling • Sponsor: • Goal: • Protect people’s identity & consumer computing from viral threats • Features: • PKI based • Non-tamperable, non-programmable personal authenticator • Hardware and VM based trust management • Sponsor: • Goal: • Container Monitoring for Homeland Security • Dynamic Supply Chain Management • Features: • Integration of RFID and environmental sensors • Energy management • Communication security • Sponsor: • Goal: • Protocols for mobile ad-hoc networks • Features: • Energy efficiency • Increased lifetime • Data aggregation • Localization • Caching • Multicasting • Sponsor: Intelligent Container IMPACT: Research Use-inspired research in pervasive computing & wireless sensor networking • Goal: • Pervasive Health monitoring • Evaluation of medical applications • Features: • Secure, Dependable and Reliable data collection, storage and communication • Sponsor: • Goal: • Evaluation of crisis response management • Features: • Theoretical model • Performance evaluation • Access control for crisis management • Sponsor: Medical Devices, Mobile Pervasive Embedded Sensor Networks BOOK: Fundamentals of Mobile and Pervasive Computing, Publisher: McGraw-Hill  Dec. 2004

  20. What’s Next? • Next Class: A long Pre-req Quiz – Just Joking! • Start reading: Fundamentals of Computer Design (Ch1) Review of ISA (Appendix B) and Pipelining (Appendix A) • Paper for Next Class: “The Coming Wave of Multithreaded Chip Multiprocessors” J. Laudon and L. Spracklen, IJPP, June 2007. • Join Class Google Group • http://groups.google.com/group/asucse520-fall-07-advanced-computer-architecture • Email: asucse520-fall-07-advanced-computer-architecture@googlegroups.com

More Related