Introduces the basic design of computing systems, computer operating systems, and assembly language using a RISC architecture. Describes caches and virtual memory. Covers the interface between assembly language and high-level languages, including call frames and pointers. Covers the use of system calls and systems programming to show the interaction with the operating system. Covers the basic structures of an operating system, including application interfaces, processes, threads, synchronization, interprocess communication, deadlock, memory management, file systems, and input/output control.
Feel free to come to either lecture as long as there is an available seat.
3650-01 | IV 019 | Tu/Fr 9:50-11:30am |
3650-02 | IV 019 | Tu/Fr 1:35-3:15pm |
Nat Tuck | NI 132E | Mo 2pm-3pm, Fr noon-1pm | ntuck ⚓ ccs.neu.edu |
Supraja Krishnan | Snell Library 45 | Tu 3:30pm-5:30pm | krishnan.sup ⚓ husky.neu.edu |
Nakul Camasamudram | WVH 362 | We 10am-noon | camasamudram.n ⚓ husky.neu.edu |
Tanmay Ulhas Budukh | WVH 462 | Th 8-10am | budukh.t ⚓ husky.neu.edu |
James Wu | WVH 362 | Sa 6-7pm | wu.jame ⚓ husky.neu.edu |
Samuel Vogel | SL 045 | Tu noon-1pm | vogel.sa ⚓ husky.neu.edu |
Jack Elliot | WVH 462 | Fr 3-4pm | elliott.jame ⚓ husky.neu.edu |
Computer Organization and Design: The Hardware/Software Interface
Patterson & Hennessy
Fifth Edition
We'll also be using Operating Systems, Three Easy Pieces and the Xv6 Unix Source code, available online.
Assignments will be assigned and submitted through Bottlenose.
Late assignments will be penalized 1% for every hour late, except for the last assignment which must be submitted on time for credit.
Challenge assignments are just like homework assignments, except they're significantly more difficult and will be graded more harshly.
Participation has several parts:
Homework | 65% |
Challenges | 30% |
Participation | 5% |
Here's how the semester is likely to play out. Details subject to change.
Week | Dates | Topics & Reading | Work Due |
---|---|---|---|
1 |
Sep 08 |
|
|
2 |
Sep 12 Sep 15 |
|
|
3 |
Sep 19 Sep 22 |
|
|
4 |
Sep 26 Sep 29 |
|
|
5 |
Oct 3 Oct 6 |
|
|
6 |
Oct 10 Oct 13 |
|
|
7 |
Oct 17 Oct 20 |
|
|
8 |
Oct 24 Oct 27 |
|
|
9 |
Oct 31 Nov 3 |
|
|
10 |
Nov 7 Nov 10 |
|
|
11 |
Nov 14 Nov 17 |
|
|
12 |
Nov 21 |
|
|
13 |
Nov 28 Dec 1 |
|
|
14 |
Dec 5 |
|
|
Students needing disability accommodations should visit the Disability Resource Center (DRC).
If you have been granted special accomodations either through the DRC or as a student athlete, let me know as soon as possible.
Copying code and submitting it without proper attribution is strictly prohibited in this class. This is plagiarism, which is completely unacceptable.
Details:
Collaboration and Attribution:
Since it's not plagiarism if you provide attribution, as a special exception to these rules, any code sharing with completely clear attribution will not be treated as a major offense. Instead, credit will be split between the writers of the code.
In order to qualify for this exception, every collaborator must include a prominent notice either as a multi-line comment at the top of the submitted single source file or at the top of a submitted README file identifying all collaborators.
For example, if four students work together to do a homework, the submission will be graded as usual and then the points will be split evenly four ways as long as the collaboration is clearly indicated in the submissions. Alternatively, if a student copies half their work from Stack Overflow with proper credit, they'll get half the points.
Penalities:
First Offense:
You want to post your work to Github. I want to re-use assignments next semester without students submitting old homework.