mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-01-19 07:03:56 +08:00
entered into RCS
From-SVN: r11984
This commit is contained in:
parent
a3381c2a7d
commit
b8abf72abb
23
gcc/objc/THREADS.MACH
Normal file
23
gcc/objc/THREADS.MACH
Normal file
@ -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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user