diff options
| author | Richard Kenner <kenner@gcc.gnu.org> | 1996-05-17 08:27:31 -0400 |
|---|---|---|
| committer | Richard Kenner <kenner@gcc.gnu.org> | 1996-05-17 08:27:31 -0400 |
| commit | b8abf72abbb7370d88a16fb7e2600f386fb41985 (patch) | |
| tree | b25fb51d5f4ca2d5ac3fb1471dc331ad93297c2a | |
| parent | a3381c2a7d7970f90147b47187c36853502b37f6 (diff) | |
| download | gcc-b8abf72abbb7370d88a16fb7e2600f386fb41985.zip gcc-b8abf72abbb7370d88a16fb7e2600f386fb41985.tar.gz gcc-b8abf72abbb7370d88a16fb7e2600f386fb41985.tar.bz2 | |
entered into RCS
From-SVN: r11984
| -rw-r--r-- | gcc/objc/THREADS.MACH | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/gcc/objc/THREADS.MACH b/gcc/objc/THREADS.MACH new file mode 100644 index 0000000..55de663 --- /dev/null +++ b/gcc/objc/THREADS.MACH @@ -0,0 +1,23 @@ +This readme refers to the file thr-mach.c. + +Under mach, thread priorities are kinda strange-- any given thread has +a MAXIMUM priority and a BASE priority. The BASE priority is the +current priority of the thread and the MAXIMUM is the maximum possible +priority the thread can assume. The developer can lower, but never +raise the maximum priority. + +The gcc concept of thread priorities is that they run at one of three +levels; interactive, background, and low. + +Under mach, this is translated to: + +interactive -- set priority to maximum +background -- set priority to 2/3 of maximum +low -- set priority to 1/3 of maximum + +This means that it is possible for a thread with the priority of +interactive to actually run at a lower priority than another thread +with a background, or even low, priority if the developer has modified +the maximum priority. + + |