|
|
|
Welcome to the Spring 2004 CS422 Course Homepage!
Here you can find all the information that you'll need throughout the semester. Use
the navigation bar on the left to access the course overview, lecture notes, homework,
Teaching Assistants (with office hours) and a list of references. All announcements will
be made on this page so I recommend you monitor it regularly.
If you would like to check out previous offerings of this course, see
Spring 2000,
Spring 2001,
Spring 2002,
Spring 2003.
Course Information
- Instructor: Fred Kuhns
- Class:
- Time: Monday/Wednesday 2:30 - 4:00 p.m.
- Location: Lopata, room 101
- Textbooks:
- Required:Gary Nutt, "Operating Systems",
Third Edition, Addison Wesley, 2003.
- Recommended: Gregory Andrews, "Foundations of Mutlithreaded, Parallel, and Distributed Programming",
Addison Wesley, 2000
- Newsgroup: CS422 Newsgroup
- Exams:
- Midterm Exam: Monday, 22 March.
- Final Exam: Monday 10 May, 6:00PM - 8:00PM Lopata Hall Rm. 101
Announcements
Final Exam Answers
See Final_answ.doc or
Final_answ.pdf.
Posted: Tue 11 May 04 18:58:52 by fredk
Homework 6 is posted
Posted: Wed 14 Apr 04 17:48:27 by fredk
Using select for timeouts
For project 4 you can use select for microsecond resolution timeouts.
See select_example.c for an
example of how to do this.
Posted: Mon 12 Apr 04 17:30:55 by fredk
Project4
Project 4 is posted on the homework url.
Posted: Wed 7 Apr 04 18:31:12 by fredk
Appointments for project2 and project3
If you did not receive a grade for these projects AND you turned
something in within the specified deadline THEN you may meet with the
TAs to explain your submission.
When: Wednesday, 7 April from 11:00am to 2:30pm. Show up at the
beginning of the time interval or make a specific appointment with one
of the TAs.
Where: CEC Linux lab.
Categories you may fall into:
1) (<= 80% credit) I was unable to compile code. You must compile
and demonstrate it works (see the Grade file for explanation of
results).
This group must show that their code compiles and satisfies project
requirements. Further the implementation must not look like mine.
2) (<= 60% credit) Incomplete implementation but code does compile. You
must show and explain the submitted code and bring a README file (or
have sent it in) which describes the project, design and the
steps to implement it.
This group must have code that compiles and an implementation that
does not look like mine ... it must be clear that they have used their
own design and not copied portions of mine. Further they must be able
to identify why their code does not work and how it could be fixed
(even though they may not know exactly how to do the fix).
3) (<= 40% credit) incomplete implementation and does not compile. Same
README and "code uniqueness" requirements as 2 and can receive up
to 40%.
4) (<= 30% credit) Nothing but a README file turned in, you must have a
README file that fully explains what you would have done, the design,
implementation steps etc. Can receive up to 30% credit but I am
expecting a lot for the readme file.
Posted: Fri 2 Apr 04 11:36:04 by fredk
Projects 2 and 3
Rather than have everyone make an appointment to demonstrate your
projects, it will be by invitation only. If you completed your project
and I have no questions then no invite. If your project is not self
explanatory then you will get an invite.
Posted: Mon 22 Mar 04 17:35:21 by fredk
Summary for midterm
The notes
(midterm_review.ppt or
midterm_review.pdf)
summarize some of the material for the midterm. I also suggest you
review all the class notes and homework assignments.
Posted: Wed 17 Mar 04 19:14:50 by fredk
Midterm
The midterm is scheduled for Monday 22 March and will cover all the
material through deadlocks.
Posted: Mon 15 Mar 04 19:24:50 by fredk
Late Policy for projects 2 and 3
In all fairness to those who have completed their projects on
time I will not formally change the due date and time (Midnight
on Wednesday, 17 March). The usual late policy applies: 5 points
per day for up to 3 days. After 3 days I will not accept new
submissions.
What I will do is require each of you to make an appointment
with myself or a TA to explain your submission and answer our
questions. If you did not turn in a working solution then this
is your chance to demonstrate your understanding of the project,
explain your design and describe your implementation (problems,
successes, issues, etc).
If you have a working solution then great: turn it in and make
an appointment to show off your solution. If you do
not have a working solution then turn in what you
have and add a section(s) to your README file describing your
unimplemented/non-working modules. This is your chance to
demonstrate you understand the big picture and were able to
specify a design. You must also explain the reason for not
completing your project on time (technical reasons). You will
not receive full credit but I will assign partial credit based
on both your submitted materials and your ability to articulate
your design and what you would need to do in order to complete
the project.
If you do not have a working Project 2 then you may use my
solution (all but sync.c) for your project 3. You must implement
your own version of sync.c, I leave it to you to ensure that
your code looks nothing like the code provided in sync.c
I will post available appointment times Wednesday, 17 March
(they will be for the following week).
Posted: Mon 15 Mar 04 18:56:19 by fredk
Test code for projects 2 and 3
I have added test code for project 2 (tests/testapp.c) and
project 3 (tests/callout.c). See the homework URL.
Posted: Fri 12 Mar 04 18:43:10 by fredk
Updated project 3 description
I have added a description of the wth_twait() method in the
project3 writeup (timed wait). You must implement this method for
project 3, it is defined in wth.h.
Posted: Mon 8 Mar 04 14:40:44 by fredk
Project 3 and example problems
I have posted project 3 and an example problem set. See the homework
url.
Posted: Wed 3 Mar 04 18:14:02 by fredk
More project 2 help
I have created two simple programs as examples of how to use sigsetjmp
and siglongjmp. See the description at the top of the project2
description.
Posted: Fri 27 Feb 04 13:49:16 by fredk
Homework 3
I have posted both some example problems (with answers) and homework
problems in the homework page.
Project2 source
I have placed the source for my solution to project2 in the wuthreads
directory (~cs422/wusrc/wucse/wuthreads). Of course you may look at
this source all you wish but you are not permitted to use any of it for
your implementation (with the exception of wth.h, wlog.h and wlog.c).
You may also browse the wuthreads source at
wuthread.
Posted: Wed 25 Feb 04 18:46:45 by fredk
Project2
See the homework page.
Posted: Thu 19 Feb 04 12:03:59 by fredk
performance measurement
I have placed my code for measuring several system performance metrics
in the cs422 account directories. See
/home/cec/class/cs422/wusrc/wucse/wuperf The executables are in the
SunOS and Linux subdirectories. As I recall I return the the
"round-trip" times for context switching/object creation so you will need to divide
the reported number by 2 to get the actual times. The project writeup
from last year is at (this is not an assignment for you to do)
Spring 2003 Project 2.
Posted: Thu 12 Feb 04 10:42:51 by fredk
Example code for Project1
Example Code: See ipc1.c
Posted: Sun 8 Feb 04 12:25:27 by fredk
Project 1
Your first project is now posted and is due Wednesday 18 Feb. See the
homework URL.
Quick reference guides
I've added links on the class reference URL
to some guides which you may find useful.
[an error occurred while processing this directive]
Posted: Thu 29 Jan 04 11:10:39 by fredk
Homework 1 posted
See the homework page for details
(Homework)
Posted: Wed 28 Jan 04 18:16:41 by fredk
|
