From 4e0f108f35a10fd278f2f1e0e1b1bae8d4dd9c7c Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Tue, 20 Dec 2005 18:30:03 +0000 Subject: [PATCH] Wording clarifications. --- doc/threads.texi | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/threads.texi b/doc/threads.texi index 2f42e3d..28b87fa 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -499,7 +499,7 @@ have the priority scheduler working, except possibly for priority donation, before you start work on the advanced scheduler. You must write your code so that we can choose a scheduling algorithm -policy at Pintos startup time. By default, the round-robin scheduler +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 @@ -512,6 +512,8 @@ directly control their own priorities. The @var{priority} argument to @func{thread_set_priority}, and @func{thread_get_priority} should return the thread's current priority as set by the scheduler. +The 4.4@acronym{BSD} scheduler does not implement priority donation. + The advanced scheduler is not used in any later project. @node Project 1 FAQ -- 2.30.2