Links to sections on this page:
This is a senior-level undergraduate class in computer operating systems. We will cover the principles underlying the design of various subsystems of modern operating systems, ranging from process management and virtual memory to file systems and access control. Instruction in these principles will be augmented a series of projects in which students develop these subsystems within the context of an instructional operating system.
The following schedule and topics are tentative and are subject to change without notice (and it's based on a 15-week semester).
At the end of very book chapters, there are exercises. Students should treat them as additional resources. These exercises will not be collected, graded, or dicsussed, although students are encouraged to work on them if there is time.
You will be expected to complete a sequence of kernel programming assignments which develop various components of a real operating system: process management, file systems, and virtual memory.
All projects will require a fairly strong background in C programming, which you are expected to pick up on your own. There will be 1 to 2 warmup programming assignments at the beginning of the semester to make sure that you are up to speed with C and doing multi-threading in C.
There will be 3 kernel programming assignments and they are extremely difficult and can be very very time-consuming. You can do these assignments in teams of two to four students. Since the kernel programming assignments are interrelated, you must pick a team at the beginning of the semester and stick with the team till the end of the semester. If you'd prefer, you can do the kernel assignments by yourself (although this is only recommended for students who are good programmers and are good at debugging using a commandline debugger).
All programming assignments can only be graded on a 32-bit Ubuntu 16.04 system. You will receive no credit if your program cannot run on this platform.
For more information, please see the projects web page.
A midterm and a final examination will be given. The date of the midterm examination will be posted near the top of the class home page. The date of the final examination is firm and it is also listed near the top of the class home page. Any scheduling conflicts regarding the midterm exam date must be resolved with the instructor at least one week before the exam date. General Information section of the class web page.
There are three types of exam questions that I usually ask. The first type is a calculation-type question. Pretty much anything that can be calculated/computed by running an algorithm can be asked in an exam. For example, I can ask you to compute a schedule using a particular scheduling algorithm. I can also ask you to calculate average waiting time for a particular scheduling policy. (Calculators will not be permitted during exams, but you can leave your answers as fractions for non-integer answers.) I may also ask you about what a data structure (e.g., tree, hash table, etc.) would look like after certain operations have been performed on it. Usually, for this type of questions, you must get the answer right and there is not much room for partial credits.
The second type is multiple-choice questions. Unless explicitly stated, every multiple choice questions has one or more correct answers. (Even if a question asks, "which statements are correct", it can have one or more correct answers.) Please check all the correct ones and don't check any of the incorrect ones. There is a penalty for selecting incorrect answers (you will lose 1 point for every such selection). Please note that an incorrect statement can never be a correct answer (unless the question asks you to select statements that are incorrect).
The scoring of multiple-choice questions is as follows. Multiple-choice questions are worth 2 points each and you are given 5 selections for each such question. It can have 1 to 4 correct answers. If a multiple-choice question has 1, 2, or 4 correct answers, for each correct answer that you have selected, the number of points you will get would equal 2 divided by the total number of correct answers. If it has 3 correct answers, you will get 1 point for selecting one of the correct answers and you will get 0.5 point each for selecting additional correct answers. Therefore, if you mark all the correct answers and don't mark any of the incorrect answers, you will get 2 points. But if you have selected incorrect answers, we will subtract 1 point for each such selected. In the end, if the total score for a problem is below zero, a score of zero will be assigned. Let's look at a concrete example. If a problem has 3 correct answers and you selected 2 correct ones and one incorrect one. You will get 1.5 points for the correct answers and -1 point for the incorrect answer. So, you will end up with 0.5 point. On the other hand, if you have only selected one of the correct answers and didn't select anything else, you will end up with 1 point.
The third type is to ask you to give the best answer for a given question. (If a question says, "In N words or less...", it's giving you a hint that the answer should be N words or less. You don't have to answer in N words or less. There is one exception though. If the question is of the fill-in-the-blanks type where N is small, then you must not use more than N words.)
For this type of question, you get credit for including the "best answer". You may get deductions for including "bad answers". What you need to demonstrate is that you can distinguish between answers of different quality and write down the best answer. (For these questions, there is no need to write complete English sentences when you answer exam questions. Just give me the important stuff!)
Let me give a couple of silly examples (with questions that's not in the scope of any exam).
In general, better answers may score more points. If you give very high level and generic answer that's generally true or basically just repeat the question, you probably will get very little partial credit for it! You need to answer a specific question with a specific answer. On the other hand, if the question called for a general answer and the answer you gave only applies to some specific examples, you probably will get very little partial credit for your answer. You must not give examples to answer general questions.
If I asked a question straight from the lecture slides, the best/correct answer is the one on the lecture slides. If you disagree with what's on the slides, you must complain when you are studying for the exam, i.e., before the exam. Once the exam starts, it's too late to complain that you don't like the answer on the lecture slides. In an exam, if you give an answer that's different from the lecture slides, you may receive partial credits, at the discretion the TA. Finally, I reserve the right to ask about things that I think you should know and not on lecture slides and not in the textbook.
I mentioned on the exams lecture slides that our exams are mainly about "knowledge about course material" AND "critical thinking". I think a lot of students lost points in multiple choice questions because they were not careful about reading questions and answers. If you are not very careful in reading multiple choice answers and you select an incorrect answer, you would lost 1 point and these points do add up. Since all students in CS 402 are grad students, it's reasonable to ask everyone to "think critically". For every "wrong" answer in a multiple choice question, if you think carefully (based on your knowledge about the course material), you should be able to say, "Obviously, this is wrong because of this and that", i.e., you should be able to form an argument that clearly show that a particular answer is incorrect. So, you definitely need to know the course material well enough so you can form those arguments. You also need to read every question and every answer very carefully so you won't choose an incorrect answer.
One thing I would recommend is to form a study group to study for exams. You can form a study group with your kernel teammates or teammates from another team. You can come up with your own true/false question when you read lecture slides and ask other students to figure out whether your statement is true or false. If someone answered "false", he/she must give an explanation why the answer is false. If you get into the habit of identifying exactly why a particular statement is false, I think you will be able to do the same during exams.
The grading breakdown is as follows:
The above percentages will be used to calculate a numeric score.
Two methods will be used to calculate your final letter grade:
Your class letter grade will be the higher grade based on (1) or (2).
Please also note the following:
All project assignments must be turned in on time. Late submissions will receive severe penalties. Due to clock skews, electronic submissions of projects assignments will be accepted within 15 minutes after the specified deadlines without penalties. For a project assignment, if you submit within the next 24 hours, you will receive 90% of your grade. Although right after midnight of the submission deadline, you will lose 1% every 5 minutes. When the penalty reaches the day limit, it flattens out. For example, if your submission has a timestamp that is 32 minutes after the grace period, 7% will be deducted from your assignment after grading; if your submission has a timestamp that is 1 day, 7 hours, 30 minutes, and 1 second after the grace period, you will receive a score of zero (and your assignment will not be graded). The figure below summarize the deductions for warmup assignment 1, warmup assignment 2, and kernel assignment 3.
For kernel assignment 1 and kernel assignment 2, beyond one day late, you can still submit and receive a 50% deduction, if you inform the instructor before these assignments are graded. This goes all the way to the next assignment submission deadline. The idea here is that since kernel 2 depends on kernel 1, if your kernel 1 is not working, you may end up spending all your time to get it to work in the next couple of weeks and have no time to work on kernel 2. This way, you still get 50% of your kernel 1 score and will enable you to complete kernel 2 also at a 50% deduction. The figure below summarize the deductions for kernel assignment 1 and kernel assignment 2. (Please note that this policy does NOT apply to kernel assignment 3.)
If you are unable to complete a assignment due to illness or family emergency, please send e-mail to the instructor as soon as possible to get an extension. A documented official proof of illness or family emergency is required in order to get an extension (doctor's note is required as proof of illness). In general, when you get sick, it's best to see a doctor and get a note just in case you may need it later.
For kernel assignments, you can only get an extension if everyone in the team is sick. Please also understand that even if you have an approved extension, all your work must be submitted before any final exam starts (which is on the Wednesday of the final exam week). If you have a prolonged illness and cannot finish your assignment before that, your only option is to take a grade of INCOMPLETE and complete your missing assignments in the next semester. But please understand that, in this case, you are only eligible for a grade of INCOMPLETE if you cannot take the final exam due to illness. Once you have taken the final exam, this option is no longer available.
Recently, there has been a change in the policy at the Student Health Center regarding giving a "note from the doctor" for you to bring to a faculty member so that you can be execused from deadlines. Basically, they will not give you such a note any more. What they would give you is an Authorization for Disclosure of Medical Information form. With this form, you give them permissions to discuss your illness with me.
So, if you visit a doctor at the Student Health Center, please make sure you fill out one of these forms, check the "limited discussion with faculty" checkbox, get it stamped, signed, and dated by someone there (a clerk/receptionist would sign at the "witness" line), and bring it back to me. This would satisfy the "note from a doctor" requirement so that you can get an extension.
Alternatively, if you get a "Walkout Statement" from Student Health that has your name and the date of the visit, you can send a copy of that to me and that would also satisfy the "note from a doctor" requirement. If there is too much private information on the Walkout Statement, please feel free to black it out before you make a copy.
If you visit a doctor somewhere else, please either bring a "note from the doctor" or a similar authrozation letter so I can contact them. The minimum requirement is to bring a piece of paper from the doctor's office (showing that it's from the doctor's office) saying that you were there on that day. It doesn't have to say why you were at the doctor's office. But it has to show that you were there.
All requests to change grading of programming assginments must be submitted in writing within one week of the time the initial grade was announced to you. Requests must be specific and explain why you feel your answer deserves additional credit. A request to re-grade an assignment can result in the entire assignment being re-evaluated and as a result the score of any part of the assignment be increased or lowered as appropriate.
Each TA is required to use one standard when grading all the exams in his/her section. Therefore, regrade for exams is not about arguing for points but about whether the TA has made a mistake in grading or not. If you think the TA has made a mistake, you should write down (on the cover page of the exam) which problem/subproblem needs to be regraded and why you think the TA has made a mistake. Plese limit the description of your rationale to be only one sentence long (e.g., "my answer is also correct", "I deserve more partial credit", etc.). There is no need to discuss your answer or your rationale with the TA since the TA is required to grade entirely based on what you wrote on the exam paper (and thus must ignore everything you said during a regrade session).
Office hours will be held in Zoom meetings this summer. I will have to limit the time for each student to be 15 minutes max to give other students a chance. Zoom meeting has a waiting room and the wait list may be long. Therefore, there is always a possibility that by the time the office hour ends, you are still on the wait list. It may be best to e-mail your questions to me or post your questions to the class discussion forum.
I will keep the Zoom meeting running during office hour. When no one is waiting to ask me questions, I may walk away from my computer. If when you arrive to the office hour and I'm not in front of the computer, please send me an e-mail. If you know that you will arrive to the office hour at a certain time, please send me e-mail so I can make sure that I won't walk away at that time (although please understand that this is not an "appointment" since I may be talking to another student already).
Also, at this time, I'm not sure if the waiting room feature would work! The TA told me that if you login from USC, you would bypass the waiting room! Therefore, if someone is showing me his/her code, another student can easily copy the code! To make sure that this cannot happen, please only talk about your code if we are in a private meeting. This means that during office hours, if you want to share your screen, we should be looking at common course material such as lecture slides and class web pages.
There are three ways to get extra credit in this class.
Please note that due to my fairness policy, I cannot offer any individual extra credit work.
Unless otherwise specified, programming assignments and exams must be that of the individual student (for group programming assignments, the work must be completely that of the group members). It is often productive to study with other students. However, if any portions of the programming assignments are found to be shared between two (or more) students, zero credit will be given to all students concerned and all students will be disciplined. This policy is in the interest of those students who do their own work, which hopefully applies to all of you in this class.
This policy also holds for programming assignments. In this class, we will use sophisticated automated program checkers to detect cheating. Be aware that the program checkers have demonstrated very good results and are widely used within the academic community. Any student caught cheating will be given zero credit and will be disciplined.
It is the students responsibility to submit their assignments electronically in time.
For students who satisfied the prerequisite at other universities or through work experience, this course assumes that you understand data structures, basic algorithms, and UNIX programming. You should be able to write large programs in C. No special assistance or consideration will be offered if your background is inadequate.
During the semester you are responsible for completing the assigned readings, programming assignments, and exams.
You must keep up with the assigned readings. If you come to class without having read the chapter for the corresponding lecture, you're unlikely to learn anything at all from the lecture. In particular:
The instructor must treat all students equally and cannot give special treatment to any particular student. Therefore, please do not ask special favors from the instructor because of your circumstances. This may seem unfair to you because you believe that your circumstances are special (understandably, everone does). Other than the exceptions setup at the beginning of the semester (mostly for "remote DEN" students), the rule the instructor must follow is that whatever he offers you, he must offer to the entire class.
Someone students don't understand why I am so strict with rules. Some think that it's just a power trip for me. The reason for sticking to rules is that I have the responsibility of treating all students fairly! If I apply one rule to one student and don't apply the same rule to another student, I think that's totally unfair. I think fairness is very important. Without fairness, grades have no meaning. The only way I know how to be fair is to have rules that are written down clearly and stick to all the written rules. When you ask me to bend a written rule for you, please understand that you are asking me to be unfair to all other students; and therefore, I will not bend the rule for you.
Students who are registered with the Disability Services and Programs (DSP) must inform the instructor regarding the type of accommodations that have been approved by the university. Please send a copy of your Letter of Accommodation from DSP to the instructor by the end of the 3rd week of classes so that the instructor can make sure that the required accommodations will be satisfied.
Auditing "unofficially" is not permitted for this class.
If you are officially auditing this course (i.e., register for this course under the no-grade option), you will receive all the course materials as other students. But you will not be permitted to form or join a team with students who are taking this course for grades to do the kernel assignments.
E-mail is a serious communication tool. For this class, you should setup your e-mail server so that you do not drop any e-mail from me (i.e., from <firstname.lastname@example.org>).
Pretty much all class related announcements will be sent through the class Google Group. Therefore, you are required to be a member of this Google Group. As messages are posted to the class Google Group, you will receive e-mail notifications and you should read all these class-related e-mails. Please see instructions on how to get on this group (you should do this as soon as possible).
You are strongly encouraged to send private e-mail messages to me if you have questions about programming assignments or lectures. If the answer is appropriate for the entire class, I would normally anonymize the reply and send the reply through the class Google Group and bcc a copy to you. So, please don't be shy to ask questions!
One type of question I often get over e-mail or see in the class Google Group is:
Here is my understanding of X. Am I right (or is this correct)? Correct me if I'm wrong...Although this type of question is perfectly fine during office hours, this is really not a good way to ask questions over e-mail. If no one corrects you, you must not conclude that you were correct! If you see "X" defined or described in lecture slides or in the textbook, you should try to understand why it was stated that way. A better question to ask over e-mail would be to ask about why it was stated that way.
Another type of question I often get is the following:
I am thinking about not following the spec or grading guidelines and would like to do this instead. Is it acceptable (or is this okay)?What you are really asking is whether you will receive full credit or not. Please just stick to the spec and the grading guidelines.
Some students have asked to do video conferencing or voice calling because e-mailing is too inefficient. Due to my fairness policy, if I offer video conferencing or voice calling to one student, I must offer the same to all students and that's just not feasible/scalable given the class sizes of CS 402. If you have questions, please feel free to e-mail me as soon as you have them in case it has to take several rounds of e-mailing to get your questions answered.
The diversity of the participants in this course is a valuable source of ideas, problem solving strategies, and engineering creativity. I encourage and support the efforts of all of our students to contribute freely and enthusiastically. We are members of an academic community where it is our shared responsibility to cultivate a climate where all students and individuals are valued and where both they and their ideas are treated with respect, regardless of their differences, visible or invisible.
(These resources below are provided for your information. Please note that the instructor has not read most of them. Please use these resources at your own risk!)
Programming (please understand that the information on these web sites may be incorrect):