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


Note: I will post important short-term notices here


General Information

Lecture:
Mon 6:00P- 8:20P Weaver CIWW 1302
Instructor: Hubertus Franke, frankeh@cs.nyu.edu
TAs/Graders: Vikram Mullachery, mv333@nyu.edu
Xiangbo Liang, xl1129@nyu.edu
Office Hours:
and
TA Assignment
[0-9] Franke: Mon 8:20 - 9:20 PM after class
[A-N] Mullachery: Tue 4:00 - 5:00 PM, 13th floor lounge
[O-Z] Liang: Wed 4:00 - 5:00 PM, 13th floor lounge
Prerequisites: Common CS knowledge and some programming skills.
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++.

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. It will allow you to get and experiment with the concept rather than spending endless hours debugging tedious operating system code.

Grades

Grades are based on the labs, the midterm and final exam, each being important. The weighting will be:
Lab Assignments55%
MidTerm15%
Final30%
This is a graduate level class, so I am looking for lively interactions during the class and not just presence.
The midterm will be given on TBD.
The final will be given on TBD.


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

DateTopicHandouts ReadingsAssignments
6/1
Introduction: Computer System Architectures (what does the OS manage)
Class Overview ,
Introduction to O/S
Chapter 1
lab1 (6/16)
6/8
Processes and Threads
Operating System Structures,
Process & Threads
Chapter 2.1 & 2.2


6/15
Scheduling
Process/Thread Scheduling Chapter 2.3+
lab2 (6/30)
6/22
Concurrency Concurrency
Chapter 2.3+ , Chapter 6

6/29
Memory Management 1
Memory Management 1
Chapter 3

7/6
MIDTERM (60Mins) + Memory Management 2
Memory Management 1 (cont)
Chapter 3
lab3 (7/21)
7/13
Memory Management 3
Memory Management 2

7/20
I/O
Input/Output Chapter 5 lab4 (8/4)
7/24 (pulled forward due to conflict on 7/27
File Systems
FileSystems Chapter 4

8/3
Networking/Advanced Topics/ Review
Networking
AdvancedTopics
(slides only)

8/10
FINAL





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.
  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/summer2015/courses
Graduate cs.nyu.edu schedule: http://cs.nyu.edu/webapps/summer2015/Graduate/courses
Academic integrity policy: http://cs.nyu.edu/web/Academic/Graduate/academic_integrity.html

http://cs.nyu.edu/courses/summer15/CSCI-GA.2250-001/index.html