Keith Marzullo, APM 4824, 858 534-3729. Office hours Mondays 1.00-3.00 or by appointment. Often, the fastest way to get an answer from me is via e-mail to marzullo@cs.ucsd.edu. If you just stop by, then I'll see you then or we'll find a time that we can meet.TAs
Classroom
Center Hall 119 on Tuesdays and Thursdays from 5:30 - 6:50PM (at least it isn't at 8 AM!).Discussion Session
WLH 2206 on Wednesdays at 1:25 to 2:15PM.Text
Operating System Concepts, Sixth Edition by Silberschatz, Galvin and Gagne. I'll be pointing you to a few papers when we cover issues that are not discussed very well in the textbook.Discussion board
Sponsored by discus.
| Homeworks | 20% (each worth 5%) |
| Midterm | 20% |
| Final | 30% |
| Programming projects | 30% (each worth 10%) |
Homeworks There will be four homework assignments. Please turn in your homeworks in class. Do not turn in handwritten homeworks (we often can't read them): prepare them using Word, LaTex, or some other document preparation system.
The homeworks are by the beginning of lecture. We will not accept late homeworks.
Homework 1 available April 2 and due April 11. Solutions.Midterm The midterm will be given in class on 9 May 2002. It will be an open textbook and open notes test. As usual, this means that I'll ask questions that are not easily answered by looking them up in the textbook. The homeworks are a good approximation of what the midterm (and final) questions will look like.
Homework 2 available April 18 and due April 30. Solutions.
Homework 3 available May 9 and due May 23. Solutions.
Homework 4 available May 23 and due June 6. Solutions.
Final The final is on Wednesday, June 12 from 7 to 10 PM. Like the midterm, it will be an open textbook and open notes test.
Projects There will be three programming projects:
Project 1 due Sunday, April 28 at 11:59 PM.You will be working in teams, the size of which we'll define during the first week of class.
Project 2 due Sunday, May 26 at 11:59 PM.
Project 3 due Friday, June 7 at 11:59 PM.
You can find details on how to submit projects on the individual project description pages.
The programming projects will be in C. We'll offer some remedial instruction for students who are not comfortable programming in C.
Handouts I don't produce individual lecture notes for each lecture because I think they tend to disengage a student. Instead, I have sets of notes for the different major topics of the course. My lectures follow these notes fairly closely.
(This list will grow throughout the quarter).
|
|
Lecture |
|
Homework |
|
| Apr 2 | 1 | Processes | ||
| Apr 4 |
|
Mutual exclusion
Implementation of processes |
||
| Apr 9 |
|
Semaphores | ||
| Apr 11 |
|
Producer consumer | HW1 due | |
| Apr 16 |
|
Monitors | ||
| Apr 18 |
|
Deadlock | ||
| Apr 23 |
|
Deadlock | ||
| Apr 25 |
|
Memory management | P1 due Sunday, 28 April | |
| Apr 30 |
|
Paging and segmentation | HW2 due | |
| May 2 |
|
Page replacement | ||
| May 7 |
|
Working set | ||
| May 9 | MIDTERM on first seven lectures | |||
| May 14 |
|
Processor Scheduling | ||
| May 16 |
|
Secondary storage | ||
| May 21 |
|
File systems basics | HW 3 due | |
| May 23 |
|
Logical file systems | P2 due Sunday, 26 May | |
| May 28 |
|
File system case studies | ||
| May 30 |
|
Security and protection | ||
| June 4 |
|
Authentication | HW 4 due | |
| June 6 |
|
(TBA) | P3 due Friday, 7 June | |
| June 12 | FINAL on all lectures |
My lectures don't follow the textbook very well, but you should read the book. I will clarify differences in terminologies between me and Silberschatz's book and will refer to examples in the text.
Here is a mapping of what I will cover in lecture to the related material
in the text:
| Lectures | Chapters |
| 1-5 | 7 |
| 6-7 | 8 |
| 8-11 | 9-10 |
| 12 | 6.1-6.3 |
| 13-16 | 12.1-12.7 |
| 17-18 | 18 |