|
Silberschatz, Galvin, Gagne, Operating System Concepts, 7th Edition
John Wiley & Sons, Inc. ISBN 0-471-69466-5 (other editions also acceptable) |
This course covers the principles of operating systems. It emphasizes the basic concepts of OS kernel organization and structure, processes and threads, concurrency and synchronization, memory management, file systems, and communication. It is also a project course, providing essential experience in programming with concurrency, implementing and unmasking abstractions, working within an existing complex system, and collaborating with other students in a group effort.
The course is organized as a series of lectures by the instructor, discussion sections by the TAs, reading, homework, and project assignments, and exams:
Homeworks are due at the beginning of class on the day specified. We will reduce homework grades by 20% for each day that they are late (end of class is considered late). You must hand in a hardcopy of your homework; disagreements about the contents of emailed homeworks have caused too much grief in the past.
I encourage you to collaborate on the homeworks: You can learn a lot from your fellow students. However, there can be a fine line between collaboration and cheating. Collaboration consists of discussing problems with other students and independently writing your own answers to the problems based upon those discussions; as a rule of thumb, you should be able to discuss a homework problem in the library with others, go home, and then write up your answer to the problem on your own. Cheating consists of looking at other student's homeworks and copying the answers, looking at past homeworks and/or solutions from previous versions of the class, searching on the Web, etc. The consequences of cheating will correspond to the severity (e.g., failure of the assignment, failure of the course). Cheating causes many problems for all of us -- don't do it, and save us all the grief.
The academic honesty guidelines outlined by Charles Elkan for CSE 130 apply to this course.
The course has one tutorial project and three programming projects using the Nachos instructional operating system. You will work in groups of at most four on each of the projects.
Discussion sections answer questions about the lectures, homeworks, projects, and programming environment. They may also supplement the lectures with additional material.
Your grade for the course will be based on your performance on the homeworks, midterm and final exams, and the three projects using the following weights:
The following table outlines the schedule for the course. We will update it as the quarter progresses.
| Date | Lecture | Readings | Homework | Project |
| 3/31 | Course Intro | Chapter 1, Nachos | ||
| 4/2 | OS Architectural Support | Chapter 2 | Homework 1: Out | Project 0: Out |
| 4/7 | Processes | Chapter 3 | ||
| 4/9 | Threads | Chapter 4 | Homework 1: Due | Project 0: Due Project 1: Out |
| 4/14 | Synchronization | Chapter 6.1-6.6 | Homework 2: Out | |
| 4/16 | (No lecture, work on project) | |||
| 4/21 | Semaphores and Monitors | Chapter 6.7-6.10 | ||
| 4/23 | Scheduling and Deadlock
| Chapter 6.7-6.10 | Homework 2: Due | |
| 4/26 | (Sunday) | Homework 3: Out | ||
| 4/27 | (Monday) | Project 1: Due | ||
| 4/28 | Scheduling and Deadlock | Chapters 5, 7 | ||
| 4/30 | Review | Project 2: Out | ||
| 5/3 | (Sunday) | Homework 3: Due | ||
| 5/5 | Midterm Exam | |||
| 5/7 | Memory Management | Chapter 8 | ||
| 5/12 | Paging | Chapter 9 | Homework 4: Out | |
| 5/14 | Paging (cont'd) | Chapter 9 | ||
| 5/19 | Page Replacement | Chapter 9 | ||
| 5/21 | File Systems | Chapters 10, 11 | ||
| 5/25 | (Monday) | Project 2: Due | ||
| 5/26 | FFS, LFS, and RAID | Chapter 11.8, 12.7 | Homework 4: Due Homework 5: Out |
Project 3: Out |
| 5/28 | RPC, NFS | Chapter 11.9 | ||
| 6/2 | Virtual Machine Monitors | |||
| 6/4 | Course Summary, Final Review | Homework 5: Due | ||
| 6/7 | (Sunday) | Project 3: Due | ||
| 6/9 | Final Exam: 11:30am – 2:30pm |
E. W. Dijkstra, The Structure of the 'THE'-Multiprogramming System, Communications of the ACM, Vol. 11, No. 5, May 1968, pp. 341-346.
(Additional historical background on semaphores in Wikipedia)
D. M. Ritchie and K. Thompson, The UNIX Time-Sharing System, The Bell System Technical Journal, Vol. 57, No. 6, July-August 1978, pp. 1905-1929.
C. A. R. Hoare, Monitors: An Operating System Structuring Concept, Communications of the ACM, Vol. 17, No. 10, October, 1974, pp. 549-557.
Andrew D. Birrell, An Introduction to Programming with Threads, DEC SRC Research Report 35, January 6, 1989.
Blaise Barney, POSIX Threads Programming, Lawrence Livermore National Laboratory.