This page does not represent the most current semester of this course; it is present merely as an archive.
Welcome to the work-in-progress class page for CS 3330 – Computer Architecture. This material represents the best current estimate of course flow and content.
There are two common expectations that this course does not fulfill:
Instead, you will learn
has minimal overlap with ECE/CS 2330.
assumes you did well in CS 2150. In particular, it assumes you know
has enough overlap with ECE 4435 that you may only receive credit for one of those two courses.
is prerequisite for CS 4414 (OS), CS/ECE 4457 (Networks), and a few less-commonly-offered electives. In each cases, either ECE 3430 or ECE 4435 also meets the CS 3330 prerequisite.
This is the place to get help for almost any issue. Access via Collab or from piazza.com.
At least one of the instructors of this course is a fan of anonymous feedback, which is available through Collab.
The feedback is really truly anonymous; there is no way we can find out who posted it, so posting things like
you misgraded my homework there will not be effective.
Office: Rice 208. If the door is open, you are welcome to come in.
Email: email@example.com. I generally check it once a day on business days only. Always include 3330 in the subject line.
Office: Rice 205.
Kean Finucane, Lawrence Hook, Yiling Jia, Samuel Kwong, Marzieh Lenjani, Derek McMahon, Sugat Poudel, Ethan Robertson, Jean Salac, Dylan Saunders, Kavita Sthanumurthy, Jonathan Ting, Luonan Wang, and Yan Zhuang.
Please respect the fact that our TAs are also students in other classes, with assignments and so on of their own, and limit your 3330-related contact with them to the times they have scheduled to act as TAs.
Unless they tell you otherwise, use Piazza to contact them (and make your post visible to all course staff, not just one or two of them).
All professor office hours are open, meaning we will not close the door and have a private conversation during office hours. If you have sensitive matters to discuss, please email your professor to set up a separate time to visit about them.
A copy of Bryant & O’Halleron’s Computer Systems: a Programmer’s Perspective, third edition. It is possible to survive on the second edition, but the changes to chapters 3, 4, and 5 make the 2nd edition strongly discouraged. The first edition will not work.
To be able to come to every lab. Some lab time will be used for examination and missing those labs will generally not be excused. Lab assignments will be completed within alloted lab time.
The intent is to meet policy PROV-022, which provides a
minimum standard of 1 credit ≥ 3 hours of academic work per week for 15 weeks. We target a level of work where the median student will spend approximately the following each week:
We encourage you to set aside this time on your weekly calender in advance.