X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fthreads.texi;h=ac28ba86830da78c8431fd400edd164c5d959b94;hb=13177c92575c4e0ddc1ca1600b24f5058e349bd3;hp=7964879223fb93e4ad7e67e791c1946b4b68e649;hpb=0c6f5592b956c6a5c11c3b422e523d961f8afa45;p=pintos-anon diff --git a/doc/threads.texi b/doc/threads.texi index 7964879..ac28ba8 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -40,7 +40,7 @@ The first step is to read and understand the code for the initial thread system. Pintos already implements thread creation and thread completion, a simple scheduler to switch between threads, and synchronization -primitives (semaphores, locks, condition variables, and memory +primitives (semaphores, locks, condition variables, and optimization barriers). Some of this code might seem slightly mysterious. If @@ -170,7 +170,7 @@ Infrastructure}, for more information. @item synch.c @itemx synch.h Basic synchronization primitives: semaphores, locks, condition -variables, and memory barriers. You will need to use these for +variables, and optimization barriers. You will need to use these for synchronization in all four projects. @xref{Synchronization}, for more information. @@ -447,7 +447,7 @@ When a thread is added to the ready list that has a higher priority than the currently running thread, the current thread should immediately yield the processor to the new thread. Similarly, when threads are waiting for a lock, semaphore, or condition variable, the -highest priority waiting thread should be woken up first. A thread +highest priority waiting thread should be awakened first. A thread may raise or lower its own priority at any time, but lowering its priority such that it no longer has the highest priority must cause it to immediately yield the CPU. @@ -522,7 +522,7 @@ policy at Pintos startup time. By default, the priority scheduler must be active, but we must be able to choose the 4.4@acronym{BSD} scheduler with the @option{-mlfqs} kernel option. Passing this -option sets @code{enable_mlfqs}, declared in @file{threads/init.h}, to +option sets @code{thread_mlfqs}, declared in @file{threads/thread.h}, to true when the options are parsed by @func{parse_options}, which happens midway through @func{main}.