From 179b9174016c876790bc5e22677cc9d18501a4bc Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Fri, 31 Dec 2004 19:46:36 +0000 Subject: [PATCH] Clarification. --- doc/threads.texi | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/doc/threads.texi b/doc/threads.texi index 5532f3b..06a902f 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -333,18 +333,20 @@ and options @option{-j} and @option{-r} are mutually exclusive. @section Tips There should be no busy-waiting in any of your solutions to this -assignment. Furthermore, to the greatest extent possible, resist the -temptation to directly disable interrupts in your solution by calling -@func{intr_disable} or @func{intr_set_level}, although you may find -doing so to be useful while debugging. Instead, use semaphores, locks -and condition variables to solve synchronization problems. Read the -tour section on synchronization (@pxref{Synchronization}) or the -comments in @file{threads/synch.h} if you're unsure what -synchronization primitives may be used in what situations. +assignment. + +Do your best to resist the temptation to directly disable interrupts +in your solution by calling @func{intr_disable} or +@func{intr_set_level}, although you may find doing so to be useful +while debugging. Instead, use semaphores, locks and condition +variables to solve synchronization problems. Read the tour section on +synchronization (@pxref{Synchronization}) or the comments in +@file{threads/synch.h} if you're unsure what synchronization +primitives may be used in what situations. Given some designs of some problems, there may be one or two instances in which it is appropriate to directly change the interrupt levels -instead of relying on the given synchroniztion primitives. This must +instead of relying on the given synchronization primitives. This must be justified in your @file{DESIGNDOC} file. If you're not sure you're justified, ask! -- 2.30.2