CSE221: Graduate Operating Systems

Fall 2019


Instructor


Yuanyuan Zhou, yyzhou@eng.ucsd.edu
Office Hour: Tue 11AM - 12:00PM in 3210 (more hours will be added before the final exam)


Teaching Assistant


TA: Bingyu Shen, byshen@eng.ucsd.edu
Office Hour: 11AM - noon on Wednesday and Friday, CSE 3152

TA: Haochen Huang, hhuang@eng.ucsd.edu
Office Hour: 2:00PM - 3:00PM on Monday and Friday, CSE 3152


Class Forum


Piazza


Homework and Project Submission


We will have a few written homeworks. The homeworks serve as good practice for thinking about papers and answering questions found on the final. Please turn in your homework and project report through gradescope.


Homework



Project


The course project will measure various aspects of system performance


Course Objectives


The purpose of this course is to teach computer software system structures from a design point of view. We will look at different structuring techniques, and we will examine their usage in both important historical systems and in modern systems.

In addition to learning about different system structures and different operating systems, you will learn:


Course Structure


The structure of this class is unusual in that there are no lectures or presentations during the class period. Instead, we will discuss research papers that we will have all read before each class period. The instructor will lead discussions by asking questions of students at random in class. Note that your answers to these questions form an appreciable portion of your overall grade, so it is important that you both show up to class as well as read the papers carefully.

Because of the unusual format of this class, you will not be graded on class participation during the first two weeks of class.

Occasionally, students have to miss class for one good reason or another (e.g., present a paper at a conference, go on a business trip). If you find yourself in this situation, contact the instructor ahead of time to let him know you will be gone. Since you will not be in class to participate in discussion, you are required to write a brief evaluation of the papers for the class that you will miss. Your evaluation should address the following questions:


Reading List


The course does not have a textbook. Instead, the course material will come from seminal, noteworthy, or representative papers from the literature. Each lecture (except the first) will have two assigned papers to read. You should read these papers before coming to class, and be prepared to discuss them (written evaluations are not required). Occasionally we will also list recommended papers; you are encouraged to read those, but not required. Students often find it useful to discuss papers together before the class period, and we encourage the practice (see more on collaboration below).


Grading


The grading breakdown for the course is:

Late assignments will not be accepted without prior approval from the instructor.


Collaboration


Papers. I strongly encourage you to discuss the papers with other students in the class . you may have insights that others do not, and vice versa. Often groups of students form reading groups. Note that group discussion, however, is not an effective substitute for actually reading the paper.

Homework. You can also discuss the homework problems, but you must independently complete the assignments yourself. As a rule of thumb, you can discuss a homework problem in the lounge with others, walk home, wash the dishes, and then write up your answer to the problem on your own. You cannot, however, discuss homework problems with others and then write your answers to those problems at the same time.

Project. You can complete the course project as a team. You can discuss project materials with others in the course, but your code must have been authored exclusively by members of your team; you may not copy code from another team or make your code available to others.

In-class Quizzes and Final Exam.The quizzes and final exam should be individual effort only and closed book, and no cheat sheet is allowed.

You are expected to be aware of UCSD's academic honesty guidelines. Any violation of the course or university policies will be treated very seriously, and could lead to severe repercussions. Don't cheat. It's not worth it.