Course Topics
- Computer System Performance
- Instruction Set Architecture
- Pipelining
- Instruction-Level Parallelism
- The Memory/Cache Hierarchy
Assignments
- Traditional homeworks, e.g., problems from the book, typically with
1-week notice.
- There will also be two architecture projects.
Grading: Option 1
| Homework | 10%
|
| Projects | 12.5% + 17.5% = 30%
|
| Midterm(s) | 12.5% + 17.5% = 30%
|
| Final | 30%
|
| Class participation | Slight impact.
|
Grading: Option 2
| Homework | 10%
|
| Projects | 12.5% + 12.5% = 25%
|
| Midterm(s) | 12.5% + 12.5% = 25%
|
| Final | 40%
|
| Class participation | Slight impact.
|
We will automatically choose the option that maximizes your grade.
Fine Print - Exams
- The final will be inclusive of all course material.
- You have the right to request a regrade for your test. You must submit a written explanation of
the error that was made, along with the test, within a week of it being returned. The entire test will
be regraded, so a regrade may cause your grade to decrease.
- All tests are closed book and no notes allowed.
Fine Print - Assignments
- Late assignments will not be accepted.
- There is no regrading of written homeworks, except for addition errors. No single
problem will have a significant impact on your grade.
- You may work in groups of one or two for written homeworks. Each group of two submits one writeup,
and both people receive the same grade.
- Programming projects are to be done individually. You may discuss the projects with other people,
but you may not look at other people's code.
- Typically, homework assignments may be graded based on a statistical subset of the problems in each assignment.
Integrity
- Cheating will not be tolerated and will be dealt with accordingly.
- Please review the UCSD
student handbook for more details on Academic Integrity.
- We photocopy a random sampling of the exams in order to ensure that students do not modify their tests after they
have been returned.