This is an archive of a course I taught Summer 2018, preserved here as a resource for future students.

COMPSCI/ECE 250D: Computer Architecture

Section 001, Summer 2018


Fig. 1: This computer costs more than your car.

Overview

Lecture location: Hudson 212
Lecture time: MTuWTh, 11:30PM - 1:00PM

Instructor: Dr. Tyler Bletsch
Email: Tyler.Bletsch AT duke.edu
Office Hours: TTh, 1:00PM - 2:00PM in the classroom

Recitation location: Hudson 212
Recitation time: MW, 1:30PM - 2:45PM

Undergraduate Teaching Assistants:

UTA Office Hours: Posted here

Course Textbook: David A. Patterson and John L. Hennessy. Computer Organization and Design: The Hardware/Software Interface, 5th edition, Morgan-Kaufmann. (Amazon, AddAll) — (Not the "ARM" edition or the "Revised Printing")

Links:

Schedule

#DateLectureRecitationReadingHomework due
(11:55:00pm)
1 Wed 5/16 Intro/Overview R01. Unix, text editing, and basic C Chapter 1
2 Thu 5/17 C programming (See Resources below) (Due Fri 5/18)
Homework 0
(hw0part2 binary)
3 Mon 5/21 C programming R02. Pointers and memory management (See Resources below)
4 Tue 5/22 From C to binary Sec 2.1-2.4, 3.2, 3.5
5 Wed 5/23 Assembly R03. Assembly programming with SPIM (simple.s) Sec 2.5-end
6 Thu 5/24 Assembly R03½. Bonus recitation: More SPIM Sec 2.5-end (Due Fri 5/25)
Homework 1
homework1-kit.tgz,
prog.c
Mon 5/28 Memorial day -
7 Tue 5/29 Combinational logic Sec 4.1-4.2, B.1-B.3, B.5. basic_logic.circ
8 Wed 5/30 Sequential logic R03¾. Optional: SPIM abbreviated
^ (Recitation 3 but shorter. Optional. Complete if you still have questions about calling conventions.)
R04. Digital design with Logisim
   ^ (at least Q1-2) 		Sec B.7-B.11
9 Thu 5/31 Finite state machines, Datapath design Sec B.10, 4.3-4.4,
combo_lock.circ 		(Due Thu 5/31)
Homework 2 homework2-kit.tgz,
prog_part.c
10 Mon 6/4 Exceptions/interrupts/syscalls (latter part of deck) R04. Digital design with Logisim (Q3+)
R05. Using Logisim for larger projects 		Sec 4.9
Tue 6/5 MIDTERM Study guide
Practice midterm
(blank version)
11 Wed 6/6 Memory hierarchies (first part of deck) R06. Register file and ALU Sec 5.1-5.5 (Due Wed 6/6)
Homework 3
homework3-kit.tgz
12 Thu 6/7 Caches (latter part of deck) Sec 5.1-5.5
13 Mon 6/11 Caches (latter part of deck) R07. Caching and memory (memdance.c) Sec 5.1-5.5
14 Tue 6/12 Virtual Memory Sec 5.6-5.9
15 Wed 6/13 Virtual Memory R08. Cache+virtual memory examples Sec 5.6-5.9
16 Thu 6/14 I/O Sec A.8 (Due Thu 6/14)
Homework 4,
homework4-kit.tgz,
TA Guide to HW4,
Dramatic intro
17 Mon 6/18 I/O R09. HW5 prep Sec 4.5-end
18 Tue 6/19 Pipelined cores Sec 4.5-end
19 Wed 6/20 Pipelined cores R10. Pipeline exercises Sec 4.5-end
20 Thu 6/21 Multicore Chapter 6 (Due Thu 6/21)
Homework 5
homework5-kit.tgz,
Dramatic intro
21 Mon 6/25 Intel x86 R11. Review for final Example code,
Intel developer manual
(pages 1..3908)
Wed 6/27 Final exam: 2pm-5pm Study guide
Practice final
Reference sheet
 ↓ Deadline extended to Thu!
(Due Thu 6/28 @ 3pm, *optional*)
Extra credit,
Tar files

Syllabus & policies

Course synopsis

Computer structure, machine language, instruction execution, addressing techniques, and digital representation of data. Computer systems organization, logic design, microprogramming, and interpreters. Symbolic coding and assembly systems.

Prerequisite: Computer Science 201 or consent of instructor.

Grading breakdown

This course will require readings from the textbook, problem sets, programming assignments, and digital logic design. Grading breakdown:

Category%
Homework55%
Midterm exam15%
Final exam25%
Recitation5%

Homework grading

You are expected to complete the homework individually unless otherwise stated. However, you may discuss topics covered in the class.

Late homework submissions incur penalties as follows:

NOTE: If you feel in advance that you may need an extension, contact the instructor. We can work with you if you see a scheduling problem coming, but extensions cannot be granted at or near the due date!

Your homework grade will be based on what you submit to Sakai and when you submit it. The common excuses listed below will be rejected for the reasons shown:

ExcuseThing you could have done which invalidates excuse
My internet was slow or flaky so my submission was late.Submit with plenty of margin. There's no reason the assignment can't be submitted HOURS OR DAYS in advance.
I meant to submit, but I forgot to click the submit button.After submission, leave and re-visit the submission page to make double-sure your file is uploaded properly.
My computer broke and I lost my work!It's the modern era. Use one of the dozens of data mirroring or backup services: Dropbox, Google Drive, Box (free at Duke!), Crashplan, or just good old fashioned local backups. You should be able to set your laptop on fire and lose zero bytes of work.
I submitted the wrong file, let me send you the right file!After submission, re-download your files from Sakai to verify it's correct. Test it from scratch to ensure it's what you expect.
One tiny thing was wrong, and I can fix it! Let me get a regrade!The time to find those bugs is before submission. When you've built your program/circuit, you're not done...that's when testing begins! Test your solution under a variety of conditions. See here for a primer on software testing.
I didn't understand the requirements, let me fix my program and get a regrade!If you're the slightest bit unsure if your program meets the requirements, ask for clarification in lecture, recitation, or Piazza. If you're worried your submission won't pass our testing, run through it with a TA or the instructor.

I'm not trying to be a jerk, but this is the part of your academic career where we build individual competence, and as in the real world, oversights can be costly.

Recitation grading

Recitation is where you'll learn concrete skills to complement the lecture's theoretical material, and is essential. Recitation grading works as follows:

Grade appeals

All regrade requests must be in writing. Email the TAs with your questions. After speaking with the TAs, if you still have concerns, contact the instructor

All regrade requests must be submitted to the instructor no later than 1 week after the assignment was returned to you.

Academic integrity

I take academic integrity extremely seriously. Academic misconduct will not be tolerated, and all suspected violations of the Duke Undergraduate Honor Code will be referred to the Office of Student Conduct. A student found responsible for academic dishonesty faces formal disciplinary action, which may include suspension. A student twice suspended automatically faces a minimum 5-year separation from Duke University.

In addition to the measures taken by the Office of Student Conduct, the affected assignment(s) will receive zero credit, or possibly -100% in egregious cases.

If you are considering this course of action, please see me instead, and we can work something out! I want every student in my course to be successful.

Resources

Back to Dr. Bletsch's page