CS385 - Syllabus
|| Dr. Jakob Eriksson <firstname.lastname@example.org>
|| 3:30-4:45 pm TR, in 209 BH
|| 4-4:50 pm W, in 210 DH
| Office hours
|| Wed 4:50-6 pm (in ERF 2054)
| Teaching Assistant
|| Timothy Merrifield <email@example.com>
| TA Office Hours
|| FRI 1-2, M 11-12 (in ERF 2054)
| Lab Phone
By the end of this course, you will have a good understanding of the main elements that work together to form an Operating System. You will have significant experience with C programming for low-level application development, and some exposure to operating system development. You will have acquired familiarity with standard tools for revision control, debugging, application performance and system diagnostics.
While the class combines theory and practice, there will be a focus on practical demonstrations in lecture and extensive hands-on programming experience. Plan to spend 10 +/- 5 hours per week on homework programming, depending on your current proficiency.
We will be using the 8th edition of the main textbook below, but you should be able to get by with the 7th edition as well.
Operating System Concepts
8/e Silberschatz, Galvin and Gagne
All assignments are done in C. This is an excellent (and classic) introduction to the language.
The C Programming Language Kernigan and Ritchie
additional materials will be supplied throughout the course in the form of URLs.
This class is programming intensive, with all assignments done in C. C programming will be taught in the class, but our approach to C will be based on a prior understanding of assembly language. CS366 is a required prerequisite: concurrent enrollment only with instructor consent, and strongly not recommended unless you have prior assembly experience.
Evaluation will be done through 1 midterm (20 points), 1 final (30 points) and 10 homeworks (75 points). Totals of 100 points or higher will count as 100 points for the purpose of the final grade. Grades will be based on a relative curve, determined after the final exam.
Consulting with your classmates on assignments is encouraged, except where noted. However, turn-ins are individual, and copying code from your classmates is considered plagiarism. For example, give the question "how did you do X?", a great response would be "I used function Y, with W as the second argument. I tried Z first, but it doesn't work". An inappropriate response would be "here is my code, look for yourself".
To avoid suspicion of plagiarism, you must
specify your sources together with all turned-in materials. List classmates you discussed your homework with and webpages from which you got inspiration or copied (short) code snippets. All students are expected to understand and be able to explain their turned-in materials. Plagiarism and cheating, as in copying the work of others, paying others to do your work, etc, is obviously prohibited, is grounds for failing the course, and will be reported.
TOPICS COVERED (tentative)
- The C programming language
- from source code to executable
- relationship to assembly language
- types and expressions
- functions and function calls
- dynamic memory management
- essential programmer tools
- Purpose, Function and Structure of an OS
- User / Supervisor modes, privileged instructions
- System Calls
- Process Management
- Linking and loading
- Processes vs. Threads
- CPU Scheduling
- Interrupts, multiprocessing, simultaneous multithreading
- Synchronization mechanisms
- Race conditions and deadlocks
- Memory Management
- Operation of malloc()
- Virtual memory and paging
- Memory mapping with mmap()
- Understanding and Diagnosing Program Performance
- Profiling and the 80/20 rule
- The memory hierarchy
- Threaded vs. Event-driven programming
- Storage Management
- File systems
- Mass storage devices
- I/O and Device Drivers
- Protection and Security