Course Information

Andy Wang

COP 5611

Advanced Operating Systems

Contact Information

Andy Wang (awang@cs.fsu.edu) Office: 269 Love Building Office hours: after class

(also by appointments)

Class website: http://www.cs.fsu.edu/~awang/courses/cop5611_s2014

Objectives

Become exposed to classic and current OS literature

Gain experience in doing OS research Develop projects that lead to

publishable results

Prerequisites

COP 4610 (operating systems) CDA 3101 (computer organizations) Knowledge of the UNIX environment Proficiency in C

Course Materials

Lecture notes and papers Posted on the class website

No required textbooks

Recommended Textbooks

Tanenbaum and Van Steen, Distributed Systems Principles and Paradigms

Singhal and Shivaratri, Advanced Concepts in Operating Systems

Background Textbooks

Tanenbaum, Modern Operating Systems

Silberschatz, Galvin, Gagne, Operating System Concepts

Nutt, Operating Systems: A Modern Perspective

Kernel-Hacking Aids

Nutt, Kernel Projects for Linux Kernighan, Ritchie, The C

Programming Language Maxwell, Linux Core Kernel

Commentary Corbet, Rubini, and Kroah-Hartman,

Linux Device Drivers

Grading

Paper summaries and critiques 5% Project 40% Peer evaluation of projects 5% Entrance exam 5% Exam 1 10% Exam 2 10% Final 25%

Individual Critiques

Ten one-page single-spaced critiques on recent papers (< 1 yr), from the following venues, or from other venues with prior approval: Conferences: SOSP, OSDI, EuroSys,

HotOS, HotStorage, HotCloud, Usenix FAST, Usenix ATC, Sigmetrics, ASPLOS, Usenix Security, StorageSS, MobiCom, MobiSys

Side Note: Research Cycle

Having an idea 2 months later

Submit a grant proposal to NSF 6 months later

Funded 3 months later

Prototype built

Submit to WIP 6 months later

Evaluation done WIP published

3 months later Submit to a

conference 6 months later

Paper published

Critiques

One due each week Both in class and through turnitin.com

(via blackboard), for the first 10 weeks A few words on plagiarism

Dire consequences Academically Financially

Critiques

Need to address the following: Summary

Problems/existing & new approaches/results Intriguing aspects of the paper

Observations/trends/assumptions/techniques How can the research be improved?

Techniques/experiments/handling of corner cases and assumptions

Project

You need to develop a project in teams of two or three

It should take about at least 100 to 120 hours

Goal: Publishable results

Types of Papers

Survey papers Position papers Simulation papers Measurement papers System papers

Some Example Projects

Feasibility of using sound cues for debugging operating systems

Feasibility study of applying economic models for distributed resource management

Feasibility study of life-long storage of sensory inputs

Weekly Project Reports

Per person Demonstrate steady progress

Papers read Obstacles encountered New ideas Software pieces built Experiments

Project Proposal

Due on the 5th week

Group presentation All team members

are required to participate

2-page written proposal Motivation The state-of-the-art Methodology Expected results Show stoppers

Plan B Timeline

Project Proposal

Include: 5-10 references Division of labor amongst teams

Project Presentation

During the last two weeks of the course

12 to 15-page (max) written paper due by the last lecture (double column, single-space, 10-pt font)

Critiques on two other projects, not including yours

Exams

In-class and closed-book, unless specified otherwise

Essays and short answers Open research questions

Entrance Exam

Make sure that you have the necessary background

Too late to drop the class after exam 1 You need to pay extra to make up the

dropped credit hours

Overall Expectations

Not like an undergraduate course Need to take your own initiative Lots of time spent on reading, writing,

and working on your project Need to limit your course load

Find out about taking research hours