After installing the software (according to the Laboratory Instruction handout), your first step is to read and understand the partial thread system we have written for you. This thread system implements thread fork, thread completion, along with semaphores for synchronization. Run the program nachos in the threads directory for a simple test of our code. Trace the execution path (by hand) for the simple test case we provide.
When you trace the execution path, it is helpful to keep track of the state of each thread and which procedures are on each thread's execution stack. You will notice that when one thread calls SWITCH, another thread starts running, and the first thing the new thread does is to return from SWITCH. We realize this comment will seem cryptic to you at this point, but you will understand threads once you understand why the SWITCH that gets called is different from the SWITCH that returns. (Note: because gdb does not understand threads, you will get bizarre results if you try to trace in gdb across a call to SWITCH.)
The files you need to make sure you understand completely for this assignment are:
- main.cc, threadtest.cc -
- a simple test of our thread routines.
- thread.h, thread.cc -
- thread data structures and thread operations such as thread fork, thread sleep and thread finish.
- scheduler.h, scheduler.cc -
- manages the list of threads that are ready to run.
- synch.h, synch.cc -
- synchronization routines: semaphores, locks, and condition variables.
- list.h, list.cc -
- generic list management (LISP in C++).
- synchlist.h, synchlist.cc -
- synchronized access to lists using locks and condition variables (useful as an example of the use of synchronization primitives).
- system.h, system.cc -
- Nachos startup/shutdown routines.
- utility.h, utility.cc -
- some useful definitions and debugging routines.
- switch.h, switch.s -
- assembly language magic for starting up threads and context switching between them.
- interrupt.h, interrupt.cc -
- manage enabling and disabling interrupts as part of the machine emulation.
- timer.h, timer.cc -
- emulate a clock that periodically causes an interrupt to occur.
- stats.h -
- collect interesting statistics.
Properly synchronized code should work no matter what order the scheduler chooses to run the threads on the ready list. In other words, we should be able to put a call to Thread::Yield (causing the scheduler to choose another thread to run) anywhere in your code where interrupts are enabled without changing the correctness of your code. You will be asked to write properly synchronized code as part of the later assignments, so understanding how to do this is crucial to being able to do the project.
To aid you in this, code linked in with Nachos will cause Thread::Yield to be called on your behalf in a repeatable but unpredictable way. Nachos code is repeatable in that if you call it repeatedly with the same arguments, it will do exactly the same thing each time. However, if you invoke ``nachos -rs #'', with a different number each time, calls to Thread::Yield will be inserted at different places in the code.
Make sure to run various test cases against your solutions to these problems; for instance, for part one, create multiple producers and consumers and demonstrate that the output can vary, within certain boundaries.
Warning: in our implementation of threads, each thread is assigned a small, fixed-size execution stack. This limitation may cause bizarre problems (such as segmentation faults at strange lines of code) if you declare large data structures to be automatic variables (e.g., ``int buf[1000];''). You will probably not notice this during the semester, but if you do, you may change the size of the stack by modifying the StackSize defined in switch.h.
Although the solutions can be written as normal C routines, you will find organizing your code to be easier if you structure your code as C++ classes. Also, there should be no busy-waiting in any of your solutions to this assignment.