Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
139 lines (88 sloc) 5.31 KB
CIS 520 - Programming Project #1
---- GROUP ----
Benjamin Kuestersteffen <
static struct list thread_list; //List of threads waiting to be woken up
int64_t wakeup_time; //Time that thread is to be woken up (in ticks)
struct semaphore sema_wakeup; //Thread semaphore to put thread to sleep and wake up
struct list_elem timer_list_elem; //List element to attach to thread_list
---- ALGORITHMS ----
Within timer_sleep, the number of ticks is captured into a local variable, and the current thread is assigned to a local variable "t". "t"'s wakeup time is then set to the current # of ticks plus the requested sleep time.
Interupts are then disabled, and "t" is inserted into the list of sleeping threads (thread_list). Interupts are re-enabled, and the thread's semaphore is lowered, yielding the thread to the next one in the queue.
If the timer interupt handler is called, as long as the thread_list is not being modified, it will have no effect on the operation. The timer_interupt increments the number of system ticks, then checks to see if any threads are ready to be woken up. If the list is not empty, timer_interupt loops through the list, waking up all threads whose wakeup_time is <= to the current time. These threads are then removed from the list.
Once the ticks are incremented, the handler checks to see if any threads are asleep, if not it exits immeditely. If the list is not empty, the handler checks to see if the first element is ready to be woken up, if not it exits. Since the elements are sorted by time, the first element will always be the one that is ready to be woken up next.
>> A4: How are race conditions avoided when multiple threads call
>> timer_sleep() simultaneously?
>> A4:
The only time a global variable is updated, interupts are disabled. All other actions can be safely interupted, as only local variables will be updated.
>> A5: How are race conditions avoided when a timer interrupt occurs
>> during a call to timer_sleep()?
Race conditions are avoided in the same way as A4 above, by protecting all code that updates global variables. However, there is a possibility of a race condition if timer_interupt runs between the list_insert and sema_down. Since, though, sema_down will yield the thread to the next availble thread, instablility will be introduced into the system if interupts are disabled when sema_down is called. This error will only be possible if timer_sleep(0) is called, though, which is unlikely.
---- RATIONALE ----
This design has little busy waiting, and efficently sorts the threads for the interupt handler function. Unlike other implementations, it allows very little room for race conditions, with the exception of timer_sleep(0) above.
>> B1: Copy here the declaration of each new or changed `struct' or
>> `struct' member, global or static variable, `typedef', or
>> enumeration. Identify the purpose of each in 25 words or less.
>> B2: Explain the data structure used to track priority donation.
---- ALGORITHMS ----
>> B3: How do you ensure that the highest priority thread waiting for
>> a lock, semaphore, or condition variable wakes up first?
>> B4: Describe the sequence of events when a call to lock_acquire()
>> causes a priority donation. How is nested donation handled?
>> B5: Describe the sequence of events when lock_release() is called
>> on a lock that a higher-priority thread is waiting for.
>> B6: Describe a potential race in thread_set_priority() and explain
>> how your implementation avoids it. Can you use a lock to avoid
>> this race?
---- RATIONALE ----
>> B7: Why did you choose this design? In what ways is it superior to
>> another design you considered?
>> C1: Copy here the declaration of each new or changed `struct' or
>> `struct' member, global or static variable, `typedef', or
>> enumeration. Identify the purpose of each in 25 words or less.
---- ALGORITHMS ----
>> C2: Suppose threads A, B, and C have nice values 0, 1, and 2. Each
>> has a recent_cpu value of 0. Fill in the table below showing the
>> scheduling decision and the priority and recent_cpu values for each
>> thread after each given number of timer ticks:
timer recent_cpu priority thread
ticks A B C A B C to run
----- -- -- -- -- -- -- ------
>> C3: Did any ambiguities in the scheduler specification make values
>> in the table uncertain? If so, what rule did you use to resolve
>> them? Does this match the behavior of your scheduler?
>> C4: How is the way you divided the cost of scheduling between code
>> inside and outside interrupt context likely to affect performance?
---- RATIONALE ----
>> C5: Briefly critique your design, pointing out advantages and
>> disadvantages in your design choices. If you were to have extra
>> time to work on this part of the project, how might you choose to
>> refine or improve your design?