Operating Systems
CSCI-GA.2250-001, Summer 2016

Note: I will post important short-term notices here

General Information

Mon 6:00P- 8:20P Weaver CIWW 1302
Instructor: Hubertus Franke, frankeh@cs.nyu.edu
TAs/Graders: Jiakai Zhang, (jiakai.ta@gmail.com)
Office Hours:
TA Assignment
[0-9] Franke: Mon 8:20 (after class) in class room or Weaver 320
[A-Z] Zhang : Fri 3:00-4:00 CIWW 13th floor (lounge)

Prerequisites: Common CS knowledge and programming skills Four labs consists of approximately 500-600 lines of code each (give and take). This class is designated as class to emphasize programming in C and/or C++. We allow the first lab we programmed in Java or Phyton (or a commonly available language that we can actually grade). Subseqent classes will be based on C/C++.
Text book: Author: Andrew Tannenbaum
Title: Modern Operating Systems
Edition: 4th (you will also survive 3rd)
Publisher: Prentice Hall
ISBN-13: 978-0-12-3591620 or 978-0-13-6006663-2
ISBN-10: 0-13-359162X or 0-13-600663-9

Course Description

This course is an introductory course in operating systems (OS), focusing on the core concepts of operating systems. The emphasis will be on understanding general concepts that are applicable to a wide range of operating systems, rather than a discussion of the features of any one specific system. Topics that will be covered include:

Examples will be from Unix/Linux. Programming assignments will be based on C or C++ as Operatings Systems are implemented that way. You will initially not be required to have C or C++ knowledge, but after the first of four labs you will have to move over to C/C++. Each of the four labs is approximately 600 lines of code.

This course does not assume that you have taken an Operating Systems course as an undergraduate, or that you have had extensive experience working with one. In fact, if you have taken such a course or have a fair amount of practical experience with OS internals, this course is probably too elementary for you. Please take a look at the course schedule to get a sense of the topics that will be covered: if you can explain most of the terms contained there, you are likely looking for a more advanced course. We will NOT be "hacking" on an operating system but will have lab assignments that deal with the fundamental elements such as different process schedulers and memory management algorithms and I/O schedulers. It will allow you to get and experiment with the concept rather than spending endless hours debugging tedious operating system code.


Grades are based on the labs, the midterm and final exam, each being important. The weighting will be:
Lab Assignments65%
MidTerm (ain't happening)0%
This is a graduate level class, so I am looking for lively interactions during the class and not just presence.
As discussed in class there is no midterm
The final will be given on 8/8/2016.

Class Materials, Handouts, Lectures and Assignments (will be made avail before classes)

DateTopicHandouts ReadingsAssignments
Introduction: Computer System Architectures (what does the OS manage)
Class Overview ,
Introduction to O/S
Chapter 1
Lab 1 Due 6/7
5/30 Intro + Processes and Threads
Processes and Threads Chapter 2

Processes and Threads and Scheduling
Scheduling Chapter2 Lab 2 Due 6/28
Concurrency Concurrency
Chapter 6
Memory Management 1
Memory Management 1
Chapter 3

Memory Management 2
Memory Management 2
Chapter 3
Lab 3 Due 7/19
Independence Day Holiday OFF
Read the US Constitution
Chapter 5
Chapter 5 Lab 4 Due 8/2
File Systems
Chapter 4

No book chapter


Computer Accounts and Mailman Mailing List

Several labs (programming assignments) across the semester will provide practical implementations of operating system concepts such as processor scheduling and memory management. These assignments are accepted in C or C++.

Labs (aka programming assignments)

Doing Labs on non-NYU Systems

You may solve lab assignments on any system you wish, but ...

Obtaining Help with the Labs

Good methods for obtaining help include

  1. Asking the TA during office hours (see web page for their hours).
  2. Asking me during office hours or after class (see web page for my hours).
  3. Asking the mailing list or the NYU Classes forum (preferred).
  4. Asking another student, but ...
    Your lab must be your own.
    That is, each student must submit a unique lab. Naturally, simply changing comments, variable names, etc. does not produce a unique lab.

See also

Graduate cs.nyu.edu courses: http://cs.nyu.edu/webapps/summer2016/courses
Graduate cs.nyu.edu schedule: http://cs.nyu.edu/webapps/summer2016/Graduate/courses
Academic integrity policy: http://cs.nyu.edu/web/Academic/Graduate/academic_integrity.html