CSE 30341 is the one of the core classes in the Computer Science and Engineering program at the University of Notre Dame. This course introduces many different aspects of modern operating systems. Topics may include process structure and synchronization, interprocess communication, concurrency and parallelism with threads, virtual memory, resource allocation, file systems, security, and distributed systems.
Upon successful completion of this course, students will be able to:
Describe the basic components of a modern operating system.
Understand the symbiotic relationship between computer architecture and operating system design.
Discuss how operating systems provide abstractions for virtualization, concurrency, and persistence.
Construct applications that utilize processes, threads, interprocess communication, and synchronization primitives to solve problems requiring concurrent or parallel computation.
Explain how resources such as CPU time and memory are allocated and managed by the operating system.
Evaluate the trade-offs embedded in different operating system techniques, algorithms, and data structures.
Analyze the performance of applications in a variety of system contexts.
Unit | Date | Topics | Assignments |
---|---|---|---|
Unit 01: Virtualization with Processes | |||
Hardware, Operating Systems | Tue 08/27 | Syllabus, Computer Hardware, Boot Sequence Slides 00 Slides 01 Panopto | Reading 01 |
Thu 08/29 | OS Taxonomy, History, Themes Slides 02 Panopto | ||
System Calls, Processes | Tue 09/03 | System Calls Slides 03 Panopto | Reading 02 |
Thu 09/05 | Processes Slides 04 Panopto | ||
Scheduling | Tue 09/10 | FIFO, Round Robin Slides 05 Panopto | Reading 03 |
Thu 09/12 | MLFQ, Lottery Slides 06 Panopto | ||
Exam 01 | Mon 09/16 | Project | Project 01 |
Tue 09/17 | Events Slides 07 Panopto | ||
Thu 09/19 | Exam 01 | ||
Unit 02: Concurrency with Threads | |||
Threads, Locks | Tue 09/24 | Threads Slides 08 Panopto | Reading 04 |
Thu 09/26 | Locks Slides 09 Panopto | ||
Condition Variables | Tue 10/01 | Condition Variables Slides 10 Panopto | Reading 05 |
Thu 10/03 | Structures Panopto | ||
Semaphores | Tue 10/08 | Semaphores Slides 11 Panopto | Reading 06 |
Thu 10/10 | Patterns Panopto | ||
Exam 02 | Mon 10/14 | Project | Project 02 |
Tue 10/15 | Concurrency Bugs Slides 12 Panopto | ||
Thu 10/17 | Exam 02 | ||
Fall Break | |||
Unit 03: Virtualization with Memory | |||
Virtual Memory | Tue 10/29 | Address Space, Translation Slides 13 Panopto | Reading 07 |
Thu 10/31 | Free-Space Management Slides 14 Panopto | ||
Heap Management, Segmentation | Tue 11/05 | Heap Management Panopto Panopto | Reading 08 |
Thu 11/07 | Segmentation Slides 15 Panopto | ||
Paging | Tue 11/12 | Paging Slides 16 Panopto | Reading 09 |
Thu 11/14 | TLB / Multi-Level Slides 17 Panopto | ||
Exam 03 | Mon 11/18 | Project | Project 03 |
Tue 11/19 | Swapping Slides 18 Panopto | ||
Thu 11/21 | Exam 03 | ||
Unit 04: Persistence with File Systems | |||
I/O Devices | Tue 11/26 | I/O Devices Slides 19 Panopto | Reading 10 |
Thu 11/28 | Thanksgiving | ||
File Systems | Tue 12/03 | RAID Slides 20 Panopto | Reading 11 |
Thu 12/05 | File Systems Slides 21 Panopto | ||
Consistency, Integrity | Tue 12/10 | FFS, LFS Slides 22 Panopto | Reading 12 |
Thu 12/12 | Consistency, Integrity Slides 23 Panopto | Project 04 | |
Exam 04 | Thu 12/19 | Exam 04 |
Component | Points |
---|---|
Readings Weekly individual reading assignments. | 10 × 4 |
Projects Periodic group projects. | 4 × 15 |
Exams Four timed exams. | 3 × 45, 65 |
Total | 300 |
Grade | Points | Grade | Points | Grade | Points |
---|---|---|---|---|---|
A | 280-300 | A- | 270-279 | ||
B+ | 260-269 | B | 250-259 | B- | 240-249 |
C+ | 230-239 | C | 220-229 | C- | 210-219 |
D | 195-209 | F | 0-194 |
All Readings are to be submitted to your own private GitHub repository. Unless specified otherwise:
Note: As described below, there is a grace period that allows for late submissions with no penalty up to 12 hours after each deadline.
Students are expected to attend and contribute regularly in class. This means answering questions in class, participating in discussions, and helping other students.
Foreseeable absences should be discussed with the instructor ahead of time.
Recalling one of the tenets of the Hacker Ethic:
Hackers should be judged by their hacking, not criteria such as degrees, age, race, sex, or position.
Students are expected to be respectful of their fellow classmates and the instructional staff.
Any student who has a documented disability and is registered with Disability Services should speak with the professor as soon as possible regarding accommodations. Students who are not registered should contact the Office of Disabilities.
Any academic misconduct in this course is considered a serious offense, and the strongest possible academic penalties will be pursued for such behavior. Students may discuss high-level ideas with other students, but at the time of implementation (i.e. programming), each person must do his/her own work. Use of the Internet as a reference is allowed but directly copying code or other information is cheating. It is cheating to copy, to allow another person to copy, all or part of an exam or assignment, or to fake program output. It is also a violation of the Undergraduate Academic Code of Honor to observe and then fail to report academic dishonesty. You are responsible for the security and integrity of your own work.
In the case of a serious illness or other excused absence, as defined by university policies, coursework submissions will be accepted late by the same number of days as the excused absence.
Otherwise, there is an automatic 25% late penalty for assignments turned in 12 hours past the specified deadline.
No assignments will be accepted after the last day of class without the permission of the instructor.
This course will be recorded using Zoom and Panopto. This system allows us to automatically record and distribute lectures to you in a secure environment. You can watch these recordings on your computer, tablet, or smartphone. In the course in Canvas, look for the "Panopto" tool on the left hand side of the course.
Because we will be recording in the classroom, your questions and comments may be recorded. Recordings typically only capture the front of the classroom, but if you have any concerns about your voice or image being recorded please speak to me to discuss your concerns. Except for faculty and staff who require access, no content will be shared with individuals outside of your course without your permission.
These recordings are jointly copyrighted by the University of Notre Dame and your instructor. Posting them to other websites (including YouTube, Facebook, SnapChat, etc.) or elsewhere without express, written permission may result in disciplinary action and possible civil prosecution.
For the assignments in this class, you are allowed to consult printed and online resources and to discuss the class material with other students. You may also consult AI Tools such as CoPilot or ChatGPT for help explaining concepts, debugging problems, or as a reference. Viewing or consulting solutions, such as those from other students, previous semesters, or generated by AI Tools is never allowed.
Likewise, you may copy small and trivial snippets from books, online sources, and AI Tools as long as you cite them properly. However, you may not copy solutions or significant portions of code from other students or online sources, nor may you generate solutions via AI Tools.
Finally, when preparing for exams in this class, you may not access exams from previous semesters, nor may you look at or copy solutions from other current or former students.
Resources | Solutions | |
---|---|---|
Consulting | Allowed | Not Allowed |
Copying | Cite | Not Allowed |
See the CSE Guide to the Honor Code for definitions of the above terms and specific examples of what is allowed and not allowed when consulting resources.
If you are unclear about whether certain forms of consultation or common work are acceptable or what the standards for citation are, you responsible for consulting your instructor.
If an instructor sees behavior that is, in his judgement, academically dishonest, he is required to file either an Honor Code Violation Report or a formal report to the College of Engineering Honesty Committee.