CS 441 - Computer Architecture

Course Goals and Requirements

By the end of the course, you will be able to understand both the present and future of computer design for performance: parallelism. Specifically, we will cover circuit-level parallelism via circuit simulators; instruction-level transparent parallelism including pipelining, multi-issue superscalar, and out-of-order execution; vector processing including SWAR, SIMD, and GPU programming; as well as coarser-grained parallelism including multicore, multi-thread, and distributed-memory. To understand this, you will need to know at least the following topics from the course prerequisites:

• From CS321 (OS), and its prerequisite CS301 (Assembly)

  • Bits, binary, hex, octal, bitwise operations (like & | ~ ^ << >>), and why they matter

  • Basic computer hardware: CPU, arithmetic, floating-point, cache, RAM, disk, network

  • Threads, processes, virtual memory, paging, shared memory, concurrency, task switching

• From EE 341, and its prerequisite Physics 212

  • Resistance, capacitance, and how they affect circuit wiring at high speeds and long distances

  • Logic gates: and, or, not, xor, nand, nor, and how they're useful to build circuits

  • Glue logic: tristate busses, mux/demux, flip-flops, and how to build circuits with them

Calendar

Last day to drop: Friday, September 16. Midterm exam: Thursday, October 20. Last day to withdraw: Friday, October 28. Thanksgiving Break: Thursday, November 24-Sunday, November 27. Last class: Thursday, December 8. Final exam: 8am Thursday, December 15.

Student Resources

Academic Help: Google, Rasmuson Library, Academic Advising Center (509 Gruening, 474-6396), Math Lab (Chapman Room 305), English Writing Center (801 Gruening Bldg, 478-5246).

Grading

Your work will be evaluated on correctness, rationale, and insight. Grades for each assignment and test may be curved up or down if needed. Your grade is then computed based on four categories of work:

1. HW: Homeworks and machine problems, to be distributed through the semester.

2. PROJ1: a paper and in-class presentation on an architecture topic of your choice, due in October.

3. PROJ2: a software development or hardware performance analysis project, due in December.

4. MT: Midterm Exam, Tuesday, October 19.

5. FINAL: Final Exam (comprehensive), 8am Thursday, December 16.

Your overall score is then calculated as:
GRADE = 15% HW + 15% PROJ1 + 15% PROJ2+ 25% MT + 30% FINAL
This percentage score is transformed into a plus-minus letter grade via these cutoffs: A >= 93%; A- 90%; B+ 87%; B 83%; B- 80%; C+ 77%; C 70%; D+ 67%; D 63%; D- 60%; F. The grades “C-”, “F+”, and “F-” will not be given. “A+” is reserved for truly extraordinary work.

The Fine Print

At my discretion, I may round your grade up if it is near a grading boundary. Homeworks are due at midnight on the day they are due. Late homeworks will receive no credit. At my discretion, I may allow late work without penalty when due to circumstances beyond your control. Projects that are up to two weeks late may be accepted at a 50% grade penalty (e.g., on-time grade: 86%; late grade: 43%). Everything you turn in must be your own work--violations of the UAF Student Code of Conduct will result in a minimum penalty equal to THAT ENTIRE SECTION OF YOUR GRADE (e.g., one plagiarized homework question will negate an otherwise perfect grade on all homeworks). However, even substantial reuse of other people's work is fine (and not plagiarism) if it is clearly cited; you'll be graded on what you've added to others' work. Group projects (NOT homeworks) are acceptable iff you clearly label who did what work; but I do expect a two-person group project to represent twice as much work as a one-person project. Department policy does not allow tests to be taken early; but in extraordinary circumstances may be taken late. In extraordinary circumstances, such as an ice storm or infectious disease outbreak, classes may be held on Blackboard/Elluminate Live.

Course Outline (Tentative)