CS305 Computer Architecture Autumn 2011 Lecture 01 Bhaskaran Raman - - PowerPoint PPT Presentation

CS305 Computer Architecture Autumn 2011 Lecture 01

Bhaskaran Raman Department of CSE, IIT Bombay

http://www.cse.iitb.ac.in/~br/ http://www.cse.iitb.ac.in/synerg/doku.php?id=public:courses:cs305-autumn11:start

Computer Architecture

• “Architecture”
• The art and science of designing and constructing

buildings

• A style and method of design and construction
• Design, the way components fit together
• Computer Architecture
• The overall design or structure of a computer system,

including the hardware and the software required to run it, especially the internal structure of the microprocessor

CS305 Prerequisite

• Logic Design (CS210)
• Switching theory
• Number systems, computer arithmetic
• Logic circuits, combinatorial logic, K-maps
• Finite state machines in hardware
• Arithmetic unit, control unit design
• CAD, FPGA
• VHDL

CS305 Course Contents

• Computer organization, von Neumann arch.
• Instruction set design
• Measuring performance, Amdahl's law, CPI
• Datapath and control path
• Pipelining, hazards

CS305 Course Contents (continued)

• Memory hierarchy, cache design, cache

performance

• Disk storage
• RAID
• Error correction codes, Hamming codes
• I/O Buses

Relation to Other Topics/Courses

Gates, digital circuits, chips CPU, memory, I/O Instruction set Operating System (OS) Application programs

Digital logic Machine lang. Assembly lang. Higher level language

Hardware Software

CS210: Logic Design CS210: Logic Design CS305: Computer Architecture (Hardware/ software interface) CS305: Computer Architecture (Hardware/ software interface) CS347: Oper. Sys. CS347: Oper. Sys. Compilers (Impl. of PL) Compilers (Impl. of PL)

Course References

• “Computer Organization and Design: The

Hardware/Software Interface”, 3rd edition, David A. Patterson and John L. Hennessy, Elsevier (Restricted South Asia Edition).

• 4th edition available, but I'll follow 3rd edition
• Notes from other computer architecture courses

Why Important?

Q: Why do you think Computer Architecture is important (or unimportant)? Identify Computer Architecture around you

Scenario-1: Watch TV || Record

Scenario-2: SMS Gone, AC On

Scenario-3: ICU Patient Monitoring

Image source: uwhealth.org

Scenario-4: Rural Computing

Scenario-5: Horn-Ok-Please

Why Important?

• Computing central to information age
• Computer systems range from very small to very

large, low-end to super-computers

• New computing devices, end-user devices
• How are they designed? What affects their

performance?

Q: Why do you think Computer Architecture is important (or unimportant)?

Course Evaluation

• Homework assignment(s): 15%
• Quizzes: 15%
• Mid-sem: 25%
• End-sem: 45%
• Companion course: CS341: Computer

Architecture Lab

• Assembly language programming, learning concepts

through simulator (SPIM) based implementation

Students vs. Exam-Takers

• Student:

– Attend all classes, arriving on/before time – Exceptions require (1) written explanation (2) prior permission – Attention in classes – Integrity in work: exams, homeworks, labs, etc.

• Exam-takers

– Attendance optional

• Declare yourself as student or exam-taker
• Student --> exam-taker transision is easy and automatic
• Exam-taker --> student transition is hard

Student-Teacher Relationship

• Being a student is a pre-requisite for teacher-student

relationship

• (Only) By being a student, you can:
• Ask questions in class
• Request deadline extensions
• Negotiate on exam re-evaluations
• I will do my best to hold my end of the bargain

How You Learn is Important

• Aspects of “how you learn”
• Commitment and hard-work
• Time-management
• Group learning
• Integrity: most important

– Strict policy on dishonesty – Cheating OR helping cheat ==> FR grade