Computer Sciences Department
CS 537
Fall 2018
Barton Miller
CS 537: Introduction to Operating Systems

New Stuff


Barton Miller
email: email address
Office: 7363 CS
Phone: 263-3378
Office hours: click here

Course Materials

My lecture notes are available now. You should read the first section before coming to class.

Lectures and Discussion Sections

Lecture times: Tuesday/Thursday 1pm-2:15pm
1100 Grainger

Section TA Room Time Office Hours
301. Aditya Barve 1325 CompSci 1:20pm-2:10pm click here
302. Shebin Roy Yesudas 3345 Engr 3:30pm-4:20pm
303. Akhil Guliani 103 Psych 4:35pm-5:25pm
304. Matthew Crepea 1325 CompSci 12:05pm-12:55pm
305. Swati Anand 1325 CompSci 11:00am-11:50am

The sections will be used mainly to discuss important details of the programming assignments. It is also a good place to ask questions about the challenge problems, in preparation for the quizzes. Make sure that you leave room in your schedule to attend your scheduled section.

For the first two weeks of class, you must attend the discussion section for which you registered; you cannot attend one of the other discussion sections. If we have sufficient space in the rooms, we'll allow you to shift around.

Exams and Quizzes

The testing in the class will be based on weekley quizzes that will occur most weeks. The class schedule has the list of quizzes (though that will be updated as the semester progresses.

In general, quizzes will happen in class on Thursdays and last 10-20 minutes.

There will be no midterm and the final is optional. If you choose to take the final, it will be averaged into your semester's grade, as described below. You will need to sign up for the final during the last week of classes, if you wish to take it.

Below are the past quizzes with answers. You can also see the statistics for each quiz.

Programming Assignments

There will be five (possibly six) programming assignments during the semester. Details on these assignments will appear linked to the class home page and you'll get an announcement via email and Canvas when they are available. These assignments will be written in C and done on workstations running Linux. It is unlikely that you will be able to do all these assignments on your personal computer unless you have loaded a recent version of Linux.

Assignments will be done in teams of two (2). You do not need to keep the same teammate for each assignment. You can see the statistics for each program.

Challenge Problems

Most weeks, I will post one or two challenge problems, based on the lectures. These problem are for your use and do not need to be turned in. However, you will find that you will do poorly on the weekly quizzes, if you don't do the problems Solution for the problems will be discussed in section before the quiz. problem set. And the TA's and I will be happy to answer your questions about these problems and look over your solutions.

Late Work

Assignments are due at the date and time listed on the handout. Over the entire semester, you have three late days of credit. You can use these late days on different assignments (e.g., one day on each of three assignments) or all three days on one assignment. Other than these three days (or serious personal emergencies), no late work will be accepted.

Late days are 24-hour days.

Late days cannot be used on any assignment that is due during the last week of classes.

Academic Misconduct Policy

Make sure to read the the class page on Academic Misconduct Policy. This is critical to your success in the class.

You must complete the online form on the class Canvas page, acknowledging that you accept this policy. Until you hand this in, no assignments will be accepted.

Cells Phones

Please make sure to turn off your cell phone during class time. If your cell phone or beeper rings audibly during class, you will be asked to leave and not return until you meet with me in my office.

Please see the Academic Misconduct Policy for information relating to phones (and similar devices) during quizzes and exams.

Computer Facilities

We will be using the Linux workstations for this course. All students who have registered for this class should have an account.

If your personal computer has the proper compilers and libraries, you are welcome to use it for the programming assignments.

Grading Policy

If you don't take the final:
If you take the final:
Programming assignments:40% Programming assignments: 30%
Quizzes:60% Quizzes:45%
Final:0% Final:25%

Your lowest quiz grade will be dropped from the average; there will be no quizzes during the first two weeks. If you take the final exam, it will be counted as above. In the past, when I've taught this class, the class GPA has been around 3.0.

Class Schedule

The following schedule is tentative and could (and probably will) change. If you are planning on being out of town, make sure to talk with Bart before you make your plans.

Note that quizzes are on Thursdays.

Date Lectures (Tue/Thu) Discussion (Wed) Programming Assignments
Week 1 September 6 Introduction and overview, processes No section  
Week 2 September 11 & 13 Dispatching, process creation Intro to C Program 1: 537ps: writing the "ps" command.
Assigned: Sep 11
Due: Sep 27 @ 5pm
Week 3 September 18 & 20 Cooperating processes, semaphores.
Quiz 1: Processes
Intro to gdb, Makefiles
Week 4 September 25 & 27 Semaphores and Monitors
Quiz 2: Synchronizaton with semaphores
Discuss Challenge Problem 2
Week 5 October 2 & 4 Message passing, implementing synchronization
Quiz 3: Once again with Semaphores
Discuss Program 1-1 and Challenge Problem 3 Program 1-1: Using the Clang Staic Analyzer
Assigned: Sep 27
Due: Oct 3 @ 5pm
Week 6 October 9 & 11 CPU scheduling, deadlock
Quiz 4: Synchronization with Monitors
Discuss Program 2 and Challenge Problem 4 Program 2: Synchronizing the threads and shared memory
Assigned: Oct 8
Due: Oct 19 @ 5pm
Week 7 October 16 & 18 Relocation, Dynamic Address Translation and Segmentation
Quiz 5: Scheduling and Deadlock
Discuss Challenge Problem 5
Week 8 October 23 & 25 More segmentation, paging, Multi-level paging
Quiz 6: Segmentation
Discuss Program 3 and Challenge Problem 6 Program 3: 537make: writing the "make" command
Assigned: Oct 22
Due: Nov 7 @ 5pm
Week 9 October 30 & November 1 TLBs
No class Thurs
Week 10 November 6 & 8 TLBs, Virtual memory, page replacement, thrashing.
Quiz 7: Multi-Level Paging
Discuss Challenge Problem 7 Program 3-1: Using valgrind
Assigned: Nov 7
Due: Nov 14 @ 5pm
Week 11 November 13 & 15 Page replace algorithms, Clock.
Quiz 8: TLB's
Tues: Review discussion on C, dynamic memory allocation, and debugging with GDB (Adi)
Discuss Challenge Problem 8
Week 12 November 20 & 22 Working set
No class Thursday: Thanksgiving
No section: Thanksgiving Program 4: Safe Malloc
Assigned: Nov 15
Due: Dec 4 @ 5pm
Week 13 November 27 & 29 Disk allocation and scheduling, directories, protection, file systems
Quiz 9: Page Replacement
Discuss Challenge Problem 9 and Program 4
Week 14 December 4 & 6 File systems
Quiz 10: File systems
Discuss Challenge Problem 10
Week 15 December 11 & 13 Advanced topics (Tuesday).
No quiz
No class Thursday
Review for optional final  
Finals December 15 Optional Final Exam: 12:25pm-2:25p
Note: If you want to take the final, you need to email Bart and get a confirmation back. Only those students confirmed will be able to take the exam.

Credits and Hours

This course conforms to the standard Carnegie unit of instruction. It is for 4 credits. There are two 75 minute lectures and one 50 minute discussion section per week. In addition, there will be approximately 8 hours of out-of-class (homework) per week. Instruction covers a period of 15 weeks.

Community Standards

Our class is a safe, supportive and accepting environment. The instructors and students are expected to demonstrate respect for others in class regardless of age, race, gender, religion, nationality or abilities.

Learning Outcomes

Disability Accomodations

The University of Wisconsin-Madison supports the right of all enrolled students to a full and equal educational opportunity. The Americans with Disabilities Act (ADA), Wisconsin State Statute (36.12), and UW-Madison policy (Faculty Document 1071) require that students with disabilities be reasonably accommodated in instruction and campus life. Reasonable accommodations for students with disabilities is a shared faculty and student responsibility. Students are expected to inform me of their need for instructional accommodations by the end of the third week of the semester, or as soon as possible after a disability has been incurred or recognized. I will work either directly with the you or in coordination with the McBurney Center to identify and provide reasonable instructional accommodations. Disability information, including instructional accommodations as part of a student's educational record, is confidential and protected under FERPA.

In addition to completing an electronic Faculty Notification Letter request through McBurney Connect, it is important for students to contact the me directly by the end of the third week of the semester to set up a meeting to discuss implementation of any necessary accommodations. This early communication helps ensure that accommodations can be implemented in a timely manner. For example, if an alternative exam room is needed, arrangements must be made well in advance of an exam date to ensure room availability and to secure a room booking.

Last modified: Wed Dec 12 17:36:54 CST 2018 by bart