This is an old revision of the document!

What's New?

Refresh your pages !!!

Mar 30: A diagram to explain how to handle a page fault is posted here for your reference. The final exam covers all in this course, primarily based on the lecture notes, slides + black board, text but it stresses the second half of the course. The suggested reading list for your review: i) Introduction: lecture notes/slides only; ii) Process: 3.1– 3.4; iii) Thread: 4.1—4.4; iv) CPU Scheduling: 5.1—5.5; v) Process Synchronization: 6.1—6.6; vi) Memory management: 8.1—8.5, 8.8; vii) Virtual memory: 9.1-9.3, 9.6;

Mar 27: The memory design problem discussed in class: problem and a reference solution.

Mar 26: Lecture notes for week 10 have been posted at left tab Lecture notes. Your project mark as well as TA comments, and Q4 mark have all been posted and you can check from ePost.

Mar 8: My sample solution to midterm and the marking scheme are posted here for your reference. If you have any request regarding remarking your midterm paper, please submit your paper along with one-page document, which briefly summarizes your requests, to me by next Tuesday (Mar 13). The class evaluation for this course has been scheduled at 3:30pm on Mar 20 (Tue).

Mar 6: Assignment two (A2) has been posted and you can check from Assigments/Project. Your midterm marks have been posted and you can check from ePost.

Mar 5: Lecture notes for week 7 have been posted at left tab Lecture notes. Your A1 marks and TA's marking comments have been posted and you can check from ePost.

Mar 4: Part I of the project is closed. I am posting a sample code for you to debug your own code so that you will be able to work on the remaining scheduler(s) based on your own code. Please note that you should NOT use my code as a template for the rest of the project. Otherwise, your codes may not pass plagiarism tests.

Feb 28: Midterm term (Mar 1) will be held in classroom CB121. Please come to the place as soon as you can so that we can start at 2:30pm sharp. The project (Part I) has been extended to midnight of Mar 3 (Saturday).

Feb 24: You can review some examples discussed in class. You can also download a previous midterm exam for you to review.

Feb 24: When you review for the midterm, you should first go over all lecture notes. Then, you need to read the following chapters and sections in the text: Chapter 1 (all sections); Chapter 2 (2.1—2.6, 2.11, 2.12); Chapter 3 (3.1— 3.4, 3.6.3, 3.7); Chapter 4 (4.1– 4.4, 4.6); Chapter (5.1—5.5, 5.8) and Chapter 6 (6.1, 6.2, 6.3).

Feb 14: A sample of Pseudo code for A1 has been posted here. Note that this code is a pseudo code and it does not compile and just for showing you the expected programming structure.

Feb 8: Project has been posted in Assigments/Project. You need to decide whether you do it individually or as a team of two (in this case, you have to find your partner in class yourself), and start to work on Part I and make sure you submit it before the first deadline.

Feb 7: Lecture notes for week 5 have been posted at left tab Lecture notes. Please refer to some examples used in class for your assignment: thrd.c, alarm.c, alarm_fork.c and alarm_thread.c.

Feb 6: TA has finished marking your A1 preparation code. Your marks and TA's comments are posted in ePost. Please refer to TA's comments and make sure you write the remaining assignments in a proper style and format. Once again, please submit an independent code of your own to avoid troubles in plagiarism testing.

Jan 31: Some due dates have been changed. Check Assigments/Project and Important Dates for details.

Jan 6: You can run the following Unix commands to show the top 10 most frequent words: “cat dataset1.txt | tr -s ' \t' '\n\n' | sort | uniq -c | sort -r -n -k1 | head -n 10”. You can use these results to debug your code.

Jan 5: Assignment 1 has been posted in Assigments/Project. Please start to work on the preparation part and make sure submit it before the 1st due date.

Jan 3: Class starts. Lecture notes for week 1-2 have been posted at left tab Lecture notes.