| Course: | Advanced Computer Architecture Computer Sciences 382M Unique Number: #56530 |
| Instructor: | Prof. Doug Burger ACES 3.432 Office hours: Wednesday 2:30 - 3:30 and Thursday 2:00 - 3:00 Phone: 471-9795 dburger@cs.utexas.edu |
| Teaching Assistant: | Simha
Sethumadhavan Office and office hours: ESB 229, Desk #4, Tuesday 1:00 - 2:00 and Friday 10:00 - 11:00 simha@cs.utexas.edu |
| Administrative assistant: | Gem Naivar ACES 3.422 Phone: 232-7460 gem@cs.utexas.edu |
| Class Meetings: | TTh 11:00-12:30, PAI
3.14 |
| Class Information: | www.cs.utexas.edu/users/dburger/teaching/cs382m-f03/ |
| Objectives: | The goal for this course is to learn the important concepts in computer architecture, including the key concepts in high-performance microarchitectures, memory systems, parallel architectures, low-level operating software, and implementation technology. The foci of the course will be both current practice and advanced research. |
| Textbook: | Computer
Architecture: A Quantitative Approach, 3rd Edition, John
Hennessey and David Patterson.
Morgan Kauffman Publishers, ISBN 1-55860-596-7, 2003. There will also be a reader of important research papers. |
| Prerequisites: | Students should have graduate standing and proficiency in basic computer architecture (CS352 or equivalent). Enrollment will be limited to 40 students. Both computer scientists and computer engineers are welcome. |
| Format: | The course will consist of two lectures per week, with an expectation of frequent class participation. The class participation grade will be based on both participation in class and having done the assigned reading. There will be four homework assignments, two midterm exams, and a significant class project, with teams of one to three students on each project. There will be no final exam. |
| Grading: |
|
| Policies/Info: | Assignments will be due at the beginning of
class on the assigned day in class. Your programming assignments will
be submitted
electronically and will require you to use your departmental Unix
account. Please do not email your assignments to the teaching staff.
Programming assignments will be graded on correctness, readability,
style, and
documentation.
You have a "late account" of 3 days for the term which you can spend any way you choose for your assigments. For example, you can turn in three homework assignment one day late each, or one homework assignment 3 days late, without penalty. An assignment is late if it is not turned in at the beginning of your assigned discussion section. It is one day late until midnight of the day after it is due, two days late from then until midnight of the second day, and three days late from then until midnight of third day. Once you have exhausted your late account, no late assignments will be accepted. You are responsible for turning in your assignment to your discussion section TA. Weekends count as one late day. The departmental homework drop box will not be used. Academic Misconduct Policy You are free to discuss the course material with your classmates and are encouraged to form study groups for the exams. However, collaboration on homework or programming assignments is not permitted. Helping a friend understand the intent of a homework or programming assignment specification (i.e. discussing approaches in the abstract) is permitted. Looking at someone else's solutions or code (and/or copying it) is expressly forbidden. Working together too closely (e.g. designing solutions together or sharing code) should be aware that this is a form of cheating called collusion. Penalties for academic misconduct typically include a failing grade in this course. The homework, programs, and exams must be the work of students turning them in. University policy (see Dean of Students' policies on academic integrity) will be followed strictly. We urge everyone in the class to take appropriate measures for protecting one's work. You should protect your files, homework solution sheets, etc. as deemed reasonable. Studying for tests together is permitted and encouraged. Please come talk to us if you are unsure about how to work together with your friend in a legal, helpful manner. It is always better to ask your professor. You are responsible for knowing about all material posted to the web site and sent to the course email list. |