mirror of
https://git.rtems.org/rtems-docs/
synced 2025-05-17 21:11:43 +08:00
c-user: Use sphinx glossary support
Terms can be referenced via :term:`XYZ`.
This commit is contained in:
parent
2e0a2a06a1
commit
3e005fed9a
File diff suppressed because it is too large
Load Diff
@ -359,12 +359,12 @@ Thread Queues
|
|||||||
=============
|
=============
|
||||||
.. index:: thread queues
|
.. index:: thread queues
|
||||||
|
|
||||||
In case more than one :ref:`thread <task>` may wait on a synchronization
|
In case more than one :term:`thread` may wait on a synchronization object, e.g.
|
||||||
object, e.g. a semaphore or a message queue, then the waiting threads are added
|
a semaphore or a message queue, then the waiting threads are added to a data
|
||||||
to a data structure called the thread queue. Thread queues are named task wait
|
structure called the thread queue. Thread queues are named task wait queues in
|
||||||
queues in the Classic API. There are two thread queuing disciplines available
|
the Classic API. There are two thread queuing disciplines available which
|
||||||
which define the order of the threads on a particular thread queue. Threads
|
define the order of the threads on a particular thread queue. Threads can wait
|
||||||
can wait in FIFO or priority order.
|
in FIFO or priority order.
|
||||||
|
|
||||||
In uni-processor configurations, the priority queuing discipline just orders
|
In uni-processor configurations, the priority queuing discipline just orders
|
||||||
the threads according to their current priority and in FIFO order in case of
|
the threads according to their current priority and in FIFO order in case of
|
||||||
|
Loading…
x
Reference in New Issue
Block a user